About apappu

apappu · ‎08-09-2018

@Sudheer Velagapudi How did you remove the service from Ambari? Did you used UI/API to do that? looks like there are stale Hive, oozie, ranger configs are there. You can try cleaning up those services by following https://community.hortonworks.com/articles/79546/how-to-cleanup-service-from-ambari-database.html

apappu · ‎08-08-2018

@Ilya Li code is reading from that table - check whether it has valid/correct "from_repo_version_id" and "target_repo_version_id"

apappu · ‎08-08-2018

@Sam Red I think yes - but I can confirm that running "ambari-server reset" do not wipe out any data at Namenode side

apappu · ‎08-08-2018

@Sam Red no - it just deletes all the cluster data in Ambari server database and puts default schema. It does not touch any namenode data/binaries.

apappu · ‎08-08-2018

@Ilya Li looks like you have null reference in upgrade_history table. Can you review the entries from below query and see if from_repo_version_id, target_repo_version_id are NULL. select * from upgrade_history; //Look for zookeeper entry and correct that to valid repo version id. After correcting that you would need to restart ambari server before attempting the upgrade again.

apappu · ‎08-08-2018

@Ilya Li looks like you have null reference in upgrade_history table. Can you review the entries from below query and see if from_repo_version_id, target_repo_version_id are NULL. select * from upgrade_history; //Look for zookeeper entry and correct that to valid repo version id. After correcting that you would need to restart ambari server before attempting the upgrade again.

apappu · ‎08-08-2018

@Ilya Li Are you using Ambari 2.6.2 version? For some reason your source repository is coming as null - you can refer at https://github.com/apache/ambari/blob/release-2.6.2-rc0/ambari-server/src/main/java/org/apache/ambari/server/serveraction/upgrades/ConfigureAction.java#L200 I would recommend you to downgrade and then attempt the upgrade again as upgrade is just started (3% completed)

apappu · ‎08-07-2018

This is applicable for CentOS7/RHEL6 - for CentOS7/RHEL7 please follow https://community.hortonworks.com/articles/188269/javapython-updates-and-ambari-agent-tls-settings.html Upgrading to jdk1.8.0_171 version disables some of the TLSv1_1 TLSv1 protocols and algorithms. With this only option is using TLS1_2 version but CentOS6/RHEL6 uses Python 2.6 and it does not support TLS1_2. Agent-server communication would fail with below error. WARNING 2018-04-24 16:35:10,989 NetUtil.py:124 - Server at https://***.***.***.***:8440 is not reachable, sleeping for 10 seconds...INFO 2018-04-24 16:35:20,990 NetUtil.py:70 - Connecting to https://***.***.***.***:8440/caERROR 2018-04-24 16:35:20,991 NetUtil.py:96 - EOF occurred in violation of protocol (_ssl.c:579)ERROR 2018-04-24 16:35:20,991 NetUtil.py:97 - SSLError: Failed to connect. Please check openssl library versions. To workaround this problem you can tweak /usr/jdk64/jdk1.8.0_112/jre/lib/security/java.security file in Ambari server host to enable some of the algorithms. From: jdk.tls.disabledAlgorithms=SSLv3, RC4, MD5withRSA, DH keySize < 1024, \ EC keySize < 224, DES40_CBC, RC4_40, 3DES_EDE_CBC To: jdk.tls.disabledAlgorithms=SSLv3, RC4, MD5withRSA, DH keySize < 1024, \ EC keySize < 224, DES40_CBC, RC4_40 Please note that this is just a temporary workaround and it is recommended to Upgrade the OS version to use TLS1_2

apappu · ‎08-07-2018

@Saurabh If you have hostname issues while opening the Quick links from Ambari then you can configure the public hostname with your IP address in the agent hosts. then Ambari would use those name/ip address while opening. here you can find the documentation on setting up public hostname (or IP) https://docs.hortonworks.com/HDPDocuments/Ambari-2.6.0.0/bk_ambari-administration/content/ch_amb_ref_using_custom_host_names.html If you have issues inside YARN then there is very little can be done in Ambari point of view.

apappu · ‎08-07-2018

@Shobhna Dhami As Akhil explained you seems to have new hostname already in the hosts tables. You can try following workaround. 1. Modify "slnxhadoop04.dhcp.noid.in.sopra" hostname to "slnxhadoop04.dhcp.noid.in.sopra.tmp" (temporary hostnmae) in your host update file ( repeat this if you have old hostnames mapped with new hostnames ) 2. Now run "ambari-server update-host-names host_names_changes.json" 3. If 2nd step is successfull then go to step4 other wise identify problematic host and repeat step1 and step2. 4. Now create a new host update file mapping like below "slnxhadoop04.dhcp.noid.in.sopra.tmp" "slnxhadoop04.dhcp.noid.in.sopra" and run the "ambari-server update-host-names host_names_changes.json" command. This should resolve your issue.

Online	Offline
Last Visited	‎07-24-2021 08:27 PM

Member Since	‎06-20-2016 09:43 PM
Last Visited	‎07-24-2021 08:27 PM
Posts	308
Kudos received	103

Cloudera Community

Re: Adding host in HDP cluster

Re: How to check how long did Namenode take to res...

Re: How to change host connecting time out period,...

Re: how to configure the log4j in order to rotate ...

Re: Somebody can help me? I get this message when ...

Re: Removing and reinstalling A Service Causes DB ...

Re: Upgrade HDF 3.1.1.0 to HDF 3.1.2 Rolling Upgra...

Re: ambari server reset

Re: ambari server reset

Re: Upgrade HDF 3.1.1.0 to HDF 3.1.2 Rolling Upgra...

Re: Upgrade HDF 3.1.1.0 to HDF 3.1.2 Rolling Upgra...

Re: Upgrade HDF 3.1.1.0 to HDF 3.1.2 Rolling Upgra...

JDK Changes Causing Ambari Server/Agent Registrati...

Re: is it possible to change hostname fqdn to Ips ...

Re: How can I change hostname of datanodes in amba...