Member since
04-03-2019
962
Posts
1743
Kudos Received
146
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
11533 | 03-08-2019 06:33 PM | |
4912 | 02-15-2019 08:47 PM | |
4171 | 09-26-2018 06:02 PM | |
10599 | 09-07-2018 10:33 PM | |
5660 | 04-25-2018 01:55 AM |
04-22-2016
12:06 PM
@jramakrishnan - Very cool. I think it will not work after NN asks DNs to delete blocks and DN deletes those
... View more
04-22-2016
06:50 AM
@selvanand panneerselvam Can you please check NM logs on both the NMs and let me know if you find something in there.
... View more
04-22-2016
06:41 AM
@Andrea D'Orio - I'm checking, will get back to you
... View more
04-22-2016
06:33 AM
@vpoornalingam - Please correct If my understanding is incorrect over here
... View more
04-22-2016
06:32 AM
3 Kudos
@Elitsa Milanova The SSH Key you have provided, Ambari uses it for bootstrapping new node ( installing ambari agent etc. ), If you have already added nodes and installed components on them then there should be no issues, if you want to add new node and before adding new nodes your private key got changed, there should not be an issue because at the time of adding new node, Ambari should ask you for the private key again. See below screenshot Note - Passwordless SSH required between Ambari server and Ambari agent nodes only at the time of bootstrapping, once ambari-agent is up and running then communication between master and slave components happens over RPC, they don't need SSH for communication(Except for SSHFencing between two NNs if HA is configured)
... View more
04-22-2016
06:20 AM
3 Kudos
@selvanand panneerselvam I checked attached txt file and noticed that it is looking for NM FQDN with RPC Port 45454, see below logs node1.domain.net:45454 was not found in the list of running NodeManagers When you run yarn node -list -states=RUNNING command, I see the out has short hostnames without FQDN Can you please check yarn.nodemanager.address? Checking NM logs should give us a hint.
... View more
04-22-2016
06:11 AM
1 Kudo
@Venu Shanmukappa Can you please try to add username and password in jdbc string and let me know how it goes. open beeline using "beeline" command, use below string to connect to hiveserver2 !connect jdbc:hive2://<hiveserver2>:10000/default;user=LDAP_Userid;password=LDAP_Password
... View more
04-21-2016
04:57 AM
2 Kudos
@Andrea D'Orio I'm suspecting this issue is related to below apache jira tickets:
https://issues.apache.org/jira/browse/HIVE-10929
https://issues.apache.org/jira/browse/HIVE-11313 This issue should be fixed in tez version 1.2.1 If you run same query with "mr" as hive.execution.engine then it should run fine.
... View more
04-20-2016
05:40 PM
9 Kudos
If you are getting below error while refreshing client configs via Ambari UI then here are the steps to fix it!
1. Remove KERBEROS_CLIENT for problematic hosts using below curl call
curl -H "X-Requested-By:ambari"-u admin:admin -X DELETE "http://<AMBARI-SERVER>:8080/api/v1/clusters/<cluster-name>/hosts/<host-name>/host_components/KERBEROS_CLIENT"
2. Ensure from Ambari UI that KERBEROS_CLIENT got removed.
3. From Ambari UI --> goto the problematic host --> click on Add button --> select Kerberos Client
4. Installation should complete without any issue.
... View more
Labels:
04-20-2016
03:02 PM
2 Kudos
@sunil kanthety I have resolved similar issue today for one of our customer, here are the details 1. Removed KERBEROS_CLIENT for problematic hosts using below curl call curl -H "X-Requested-By:ambari" -u admin:admin -X DELETE "http://<AMBARI-SERVER>:8080/api/v1/clusters/<cluster-name>/hosts/<host-name>/host_components/KERBEROS_CLIENT 2. Ensure from Ambari UI that KERBEROS_CLIENT got removed. 3. From Ambari UI --> goto the problematic host --> click on Add button --> select Kerberos Client 4. Installation should complete without any issue.
... View more