Member since
04-13-2016
422
Posts
150
Kudos Received
55
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 1934 | 05-23-2018 05:29 AM | |
| 4970 | 05-08-2018 03:06 AM | |
| 1685 | 02-09-2018 02:22 AM | |
| 2716 | 01-24-2018 08:37 PM | |
| 6172 | 01-24-2018 05:43 PM |
06-01-2017
09:04 PM
1 Kudo
@dsun In addition to @xin.wang If all the accounts are created in AD/LDAP, if you are installing the services for the 1st time, while installing you get an option asking whether to Ambari to manage service accounts and UID's or skip managing. If you check on asking Ambari not to manage service accounts, it will automatically skip creation of local service accounts. If Ambari is already installed now you are trying to add new service where service account in AD the run below command, which will set Ambari not create any users or groups locally: /var/lib/ambari-server/resources/scripts/configs.sh
-u admin -p password -port 8080 set ambarihostserver.com clustername cluster-env ignore_groupsusers_create true Hope this helped you.
... View more
05-31-2017
03:13 PM
1 Kudo
@kerra I have increased hive.server2.thrift.max.worker.threads from default 500 to 1500 because of one issue with WinSQL Lite which was taking huge connection thread because of some bug in WinSQL Lite. What I have faced is when the connections threads reached 500 it was not allowing any new users to connect to Hiveserver2 using beeline. So I have increased it from 500 to 1500 to avoid this problem but usually, this will not happen if you are connected through beeline on edge node. 500 threads should be good enough to handle for one HiveServer2. Command to check number of threads on Hiveserver2 node: jstack -l <HiveServere2_ProccessId> | grep ".Thread.Stat" | wc -l Hope this helps you.
... View more
05-30-2017
04:10 PM
1 Kudo
@kotesh banoth: This is the generic error message, even I have got the similar error message in the past and I have used below parameters to solve it. Try if it works for you. set hive.execution.engine=tez;
set hive.auto.convert.join=true;
set hive.auto.convert.join.noconditionaltask=true;
set hive.auto.convert.join.noconditionaltask.size=405306368;
set hive.vectorized.execution.enabled=true;
set hive.vectorized.execution.reduce.enabled =true;
set hive.cbo.enable=true;
set hive.compute.query.using.stats=true;
set hive.stats.fetch.column.stats=true;
set hive.stats.fetch.partition.stats=true;
set hive.merge.mapfiles =true;
set hive.merge.mapredfiles=true;
set hive.merge.size.per.task=134217728;
set hive.merge.smallfiles.avgsize=44739242;
set mapreduce.job.reduce.slowstart.completedmaps=0.8 Are you using any HDFS encryption? Hope this helps you.
... View more
05-26-2017
06:35 PM
@suresh krish The issue seems to be with user profile, please compare the profile working Vs non-working.
... View more
05-26-2017
02:19 PM
@Nikita Kiselev Yes, we can. We need to make appropriate filters and search parameters. You can follow the below link and your AD team would be able to help you. https://cwiki.apache.org/confluence/display/RANGER/LDAP+Connection+Check+Tool
... View more
05-26-2017
02:07 PM
@Saransh Sharma In addition to @Binu Mathew If you don't want to take separate backups, and there are limited table to take, even you can use Hive Import/Export option. https://cwiki.apache.org/confluence/display/Hive/LanguageManual+ImportExport
... View more
05-26-2017
01:54 PM
@suresh krish POSSIBLE ROOT CAUSE: There are a number of possible root causes, but if all configurations have been verified as correct, it is good practice to check network connectivity between the ODBC client machine and the Hive server host.
WHAT TO CHECK: 1. In ~/.odbc.ini, under the relevant [DRIVERNAME], verify the values of HOST (hive server machine) and PORT (usually 10000). Check these values are correct and without typos. 2. From the ODBC client machine, check that the Hive server and port are accessible. Use your preferred network tools. For example: nc HOST PORT or telnet HOST PORT
If the Hive server port is not accessible from the ODBC client machine, check with your network team or adjust your network settings so that it is possible to connect to the Hive port on the Hive host from the ODBC client machine.
... View more
05-22-2017
08:12 PM
4 Kudos
Today we are using below command to sync all the AD users to get access to Ambari Views/Operation server. ambari-server sync-ldap --groups groups.txt We can't schedule cron tab because we need to pass admin credentials at the time of sync. It's hard to run daily as the users get added to the group and deleted which are managed in AD. By using below curl command we
can automate the Ambari LDAP sync. We can add this command to bash script and
schedule it using confab. Whenever new users get added/deleted to the LDAP
group, it will get automatically synced the same with Ambari Views. We need to
run below command as Ambari user. This can avoid running ‘ambari-server
sync-ldap’command. Here even no need to
run any unset proxy commands. curl -k -u admin:<password> -H
'X-Requested-By: ambari' -X POST -d '[{"Event": {"specs":
[{"principal_type": "users", "sync_type":
"specific", "names":
"sredd66,sreddyuw"},{"principal_type":"groups","sync_type":"specific",
"names": "hadoopadmin,hadoopusers"}]}}]' https://ambarihostname:8080/api/v1/ldap_sync_events
Steps to remove an LDAP group
from Ambari and still have the group in LDAP: Command to GET/DELETE groups from Ambari by not touching AD. GET:
curl --insecure -u admin:<password> -H
'X-Requested-By: ambari' -X GET https://ambarihostname:8080/api/v1/groups/
DELETE:
curl --insecure -u admin:<password> -H
'X-Requested-By: ambari' -X DELETE https://ambarihostname:8080/api/v1/groups/<group
name you wanted to delete> Let me know if you have any
questions.
... View more
Labels:
04-14-2017
02:59 PM
@Kumar Veerappan
No, Maintenance Mode supports suppressing alerts and skipping bulk operations for specific services, components and hosts in an Ambari-managed cluster. You typically turn on Maintenance Mode when performing hardware or software maintenance, changing configuration settings, troubleshooting, decommissioning, or removing cluster nodes. You may place a service, component, or host object in Maintenance Mode before you perform necessary maintenance or troubleshooting tasks. Maintenance Mode affects a service, component, or host object in the following two ways: Maintenance Mode suppresses alerts, warnings and status change indicators generated for the object Maintenance Mode exempts an object from host-level or service-level bulk operations Explicitly turning on Maintenance Mode for a service implicitly turns on Maintenance Mode for components and hosts that run the service. While Maintenance Mode On prevents bulk operations being performed on the service, component, or host, you may explicitly start and stop a service, component, or host having Maintenance Mode On. Link Hope this helps you.
... View more
04-11-2017
04:58 AM
@Josh Elser Can you please suggest the best way to suppress it. Here the scenario, I need to data in text xml format when I run the curl command. If I need to apply any parameter accross the cluster to accomplish this, please do let me know.
... View more