@Liana Napalkova And For the "Hive check failed with the message:" issue please make sure that the Hive Services are UP and running. If needed please restart the hive Service. Then before accessing just to be double sure that the Hive Services are running fine or not please perform a Hive Service Check from ambari UI as following: Ambari UI --> HIve --> "Service Actions" (Drop Down) --> Run Hive Service Check. Some times it can happen that the Ambari Hive Connection pool is having stale connections so please try restarting ambari server once if Restarting Hive Service does not help. ... View more

@Liana Napalkova Can you please check from the agent host (hive metastore host) If you have configured any "HTTP_PROXY" by any chance at the global level? On all the ambari Agent Host, in the "~/.bash_profile" or "~/.profile" profile we can add the following: export http_proxy=http://YOURPOROXY:PORT export https_proxy=https://YOURPOROXY:PORT Can you please verify if you are able to resolve the ambari Hostname from Agent machine and able to download the JAR using wget? # wget http://yyyyambarimaster1.xxxxxxxx.org:8080/resources//mysql-connector-java.jar # wget http://yyyyambarimaster1.xxxxxxxx.org:8080/resources/mysql-connector-java.jar . ... View more

@Liana Napalkova If it is not available in the available Yum repo then you will need to manually download it from: https://dev.mysql.com/downloads/connector/j/ After downloading the "(mysql-connector-java-5.1.46.zip)" OR tar version you will need to extract it and then you will find the "mysql-connector-java-xxxx.jar" file inside it that you need to put on your ambari server host. As following: # ls -l /usr/share/java/mysql-connector-java.jar Also please make sure that a synlink is created on your ambari server host as following inside /var/lib/ambari-server/resources/mysql-connector-java.jar # ls -l /var/lib/ambari-server/resources/mysql-connector-java.jar ----> /usr/share/java/mysql-connector-java.jar Then you will need to run: # ambari-server setup --jdbc-db=mysql --jdbc-driver=/usr/share/java/mysql-connector-java.jar It is instructed in the following link "Using Hive with MySQL" : https://docs.hortonworks.com/HDPDocuments/Ambari-2.6.1.0/bk_ambari-administration/content/using_hive_with_mysql.html ... View more

@Liana Napalkova You will need to make sure that the following path exist. Means on the Ambari Server there should be a symlink/jar as following which points to the path of your downloaded JAR. # ls -l /var/lib/ambari-server/resources/mysql-connector-java.jar ... View more

@Michael Bronson Yes API call performs the service start and stop in correct order. Ambari UI basically does invoke the same API calls. When we say "Start All Services" Or ":Stop All Services" from Ambari UI. ... View more

@Michael Bronson Yes, the steps looks fine to me. However it would be good to add the following steps: (Two Additional Steps) 3A. After IP Address change (Validation) . Perform a validation steps mentioned in the article: On the node: hostname # should return the short name of the host hostname -s # should return the short name of the host hostname -f # should return the FQDN On the Ambari Server: nslookup nodename.fqdn # should return the new IP address of the node 4A. After Agent restart (Validation), If possible then Check if the Hosts are getting registered properly to the Ambari Server properly or not? Either by logging in to the Ambari UI OR using the API call. To see if they are using the correct updated IP or not? # curl -u admin:admin -H "X-Requested-By: ambari" -X GET http://hdfcluster1.example.com:8080/api/v1/hosts?fields=Hosts/host_name,Hosts/i . ... View more

@Michael Bronson To understand how ambari determines to start a component please keep watching the state change in the following ambari=> SELECT component_name, current_state FROM hostcomponentstate WHERE component_name='HISTORYSERVER'; ambari=> SELECT component_name, desired_state FROM hostcomponentdesiredstate WHERE component_name='HISTORYSERVER'; . And in the mean time kill the History Server . ... View more

@Michael Bronson When the components are stopped normally (gratefully) like from Ambari UI or using API calls (or using direct DB edits) then ambari won't attempt to restart those components/services. Ambari checks the "Desired State" of the service/component is matching with the current state or not to take the decision on whether to start or not. So if a component crashes (or killed abruptly like using kill -9) or dues to some other issue then the Ambari Will still think that the component should be running but they are actually not running in that case ambari will attempt to start those component where the state are not matching as expected. ... View more