Member since
01-19-2017
3620
Posts
599
Kudos Received
360
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
977 | 04-06-2023 12:49 PM | |
471 | 10-26-2022 12:35 PM | |
977 | 09-27-2022 12:49 PM | |
1116 | 05-27-2022 12:02 AM | |
966 | 05-26-2022 12:07 AM |
05-27-2019
02:36 PM
@Adrián Gil What values do you have in /etc/host? Can you share a redacted version of your /etc/hosts and the output of $ hostname -f The below shows that you are trying to change to a value which is no different from the older value 🙂 Detail: Key (host_name)=(bigdata.es) already exists.
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2161)
at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1890)
at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255)
ERROR: duplicate key value violates unique constraint "uq_hosts_host_name"
Detail: Key (host_name)=(bigdata.es) already exists. Error Code: 0
Call: UPDATE hosts SET host_name = ? WHERE (host_id = ?)bind => [2 parameters bound] Please revert
... View more
05-27-2019
02:31 PM
@Adrián Gil What values are in your json file? Can you share a redacted version of the /etc/hosts and the output of $ hostname -f The below shows you are changing to a value which is no different from the old value 🙂 Detail: Key (host_name)=(bigdata.es) already exists.
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2161)
at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1890)
at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255) Please revert
... View more
05-26-2019
11:29 AM
@Zack Riesland Once the hostname has been changed apart from updating the ambari related see HWX changing host names please strictly follow the document. You will need to check the below properties updating the ambari.properties server.jdbc.hostname=
server.jdbc.rca.url=
server.jdbc.url= For hive, oozie and ranger related you will need to update these if the host where the databases for these components was also changed. As root user connect to your Ambari database backend and execute grant all privileges on hive.* to 'hive'@'new_host' identified by 'hive_password';
grant all privileges on hive.* to 'hive'@'new_host' with grant option; Run the above for all affected service mentioned above. You could be having an hbase to hive schema mapping issue! Please revert
... View more
05-26-2019
10:47 AM
@Akash S Any updates?
... View more
05-26-2019
10:30 AM
@Farhana Khan The initial screenshot was showing a discrepancy of edit_* on node02 with last epoch 542 and the new screenshot is that of node04 can you provide the comparison tables of the 3 nodes? Edit_* and last epoch and I would also want to see the screenshot of the Ambari UI of the Primary and Standby namenode status. To test the failover you can stop the active namenode it should failover to the standby the process could take some seconds and once the standby had transitioned to Primary then restart the Ex-primary which should become standby namenode what is the status of the ZKFailoverControllers?
... View more
05-25-2019
05:50 PM
@Farhana Khan Please keep me posted but, normally there shouldn't be an issue I have performed these steps on production clusters. I have seen the screenshot but that edits_inprogress is dated May 10 and the rest have correct date stamps. Anyways let's keep watch
... View more
05-25-2019
08:40 AM
@Shashank Naresh I guess your problem is with the network configuration. Adapter 1 should be NAT, Adapter 2 should either Wireless or LAN in my example screenshot its Realtek PCIe GBE Family controller the LAN NIC for my laptop yours could be different. See attached screenshot After saving the configuration restart the Virtual box Please revert Naresh.PNG
... View more
05-24-2019
03:02 PM
1 Kudo
@Adrián Gil Changing the hostname /etc/hosts is not enough there are the below step you MUST perform to have your Cluster working again. In Ambari Web > Dashboard, stop all services. Stop ambari-server and ambari-agents on all hosts. # ambari-server stop
# ambari-agent stop Create a file host_names_changes.json file with hostnames changes. Contents of the host_names_changes.json {
"bigdata" : {
"old_name_here" : "bigdata-es"
}
} From the directory where you saved the above file as a root user run # ambari-server update-host-names host_names_changes.json After successful execution, your ambari will update all the necessary files except the old hostnames in ambari.properties change the below values Change these 3 values in /etc/ambari-server/conf/ambari.properties server.jdbc.rca.url=
server.jdbc.url=jdbc=
server.jdbc.hostname= You will need to change also values for hive,oozie etc change according to your installation # Hive grant all privileges on hive.* to 'hive'@'bigdata-es' identified by 'hive_password';
grant all privileges on hive.* to 'hive'@'bigdata-es' with grant option; # Oozie grant all privileges on oozie.* to 'hive'@'bigdata-es' identified by 'oozie_password';
grant all privileges on oozie.* to 'hive'@'bigdata-es' with grant option; # Ranger grant all privileges on ranger.* to 'hive'@'bigdata-es' identified by 'ranger_password';
grant all privileges on ranger.* to 'hive'@'bigdata-es' with grant option; # Rangerkms grant all privileges on rangerkms.* to 'hive'@'bigdata-es' identified by 'rangerkms_password';
grant all privileges on rangerkms.* to 'hive'@'bigdata-es' with grant option; After doing the above now you can restart amabri and the ambari-agent hoping you have changed to the name in ambari-agent.ini, Start ambari-server and ambari-agents on all hosts. # ambari-server start
# ambari-agent start Before running the Ambari component startall make sure hive,oozie,ranger etc have the correct hostname in the Ambari UI Configs !! Happy Hadooping
... View more
05-23-2019
03:45 PM
@Sonali Dive https://community.hortonworks.com/questions/460/what-does-active-directory-secure-ldap-ldaps-conne.html#
... View more
05-22-2019
08:52 PM
@Farhana Khan node02 is the problem proceed with the documentation I had compiled before. follow diligently Very important always backup the files on all the nodes before starting the procedure !!!!! just a simple zip is okay and then copy over the good file from node3 or node1 /hadoop/hdfs/journal/XXXXcluster/current /* to node2 same direction and follow steps Please revert am sure will smiles 🙂
... View more