@Allen Niu Have you tried the Ambari API option to delete those client from the selected hosts? curl -iv -u admin:admin -H "X-Requested-By: ambari" -X DELETE http://<AMBARI_HOST>:8080/api/v1/clusters/<CLUSTER_NAME>/hosts/<HOST.NAME>/host_components/HIVE_CLIENT . ... View more

@ed day Looks like related to: https://community.hortonworks.com/questions/96985/how-do-i-fix-my-cluster-ambari-update-attempt.html#comment-97081 Based on the update it looks like your ambari-server binary upgrade is not completed fine. You should try doing the following to see if it works: 1. Make sure that the Ambari Repo is pointing to the correct link. So we will need to check the following file: Example: # cat /etc/yum.repos.d/ambari.repo #VERSION_NUMBER=2.4.2.0-136 [Updates-ambari-2.4.2.0] name=ambari-2.4.2.0 - Updates baseurl=http://public-repo-1.hortonworks.com/ambari/centos6/2.x/updates/2.4.2.0 gpgcheck=1 gpgkey=http://public-repo-1.hortonworks.com/ambari/centos6/RPM-GPG-KEY/RPM-GPG-KEY-Jenkins enabled=1 priority=1 2. If you see that it is not pointing to the correct ambari repo then you should download the correct repo file for correct OS (like CentOS6). Example: For ambari 2.4.2 you can refer to: http://docs.hortonworks.com/HDPDocuments/Ambari-2.4.2.0/bk_ambari-upgrade/content/upgrade_ambari.html # wget -nv http://public-repo-1.hortonworks.com/ambari/centos6/2.x/updates/2.4.2.0/ambari.repo -O /etc/yum.repos.d/ambari.repo 3. Now you should perform a yum clean # yum clean all # yum info ambari-server 4. Now perform a Yum Upgrade. # yum upgrade ambari-server -y OR else try reinstalling the ambari-server that will fix the missing JAR issue during last installation: # yum reinstall ambari-server . Now verify if all JARs are of correct version or not. Just for safety try running the ambari upgrade command (just to make sure that ambari DB schema is also upgraded). NOTE: You should take a Ambari DB Dump before running the ambari server upgrade command just to make sure that we have a safe copy of the ambari DB dump. # ambari-server upgrade # ambari-server start . ... View more

@Mohit Varshney Did you try using the Ambari UI "Sqoop" --> "Service Actions" --> "Delete Service" option to delete Sqoop client ? Else you can try the Ambari API approach as well to delete the sqoop as following: curl -iv -u admin:admin -H "X-Requested-By: ambari" -X DELETE http://${AMBARI_HOSTNMAE}:8080/api/v1/clusters/Sandbox/services/SQOOP . ... View more

@Pradhuman Gupta Usually this kind of issue indicates a corrupted "vmdk" image file. So please check the "md5sum" result of the file that you downloaded to make sure that it is not corrupted. You can find the md5sum result of your sandbox vm from: https://hortonworks.com/downloads/#sandbox Also you might want to refer to VMWare Sandbox prerequisite:https://hortonworks.com/hadoop-tutorial/hortonworks-sandbox-guide/#section_3 . ... View more

@Kumar Veerappan In addition to Mugdha's comment, the expected behaviour for the maintenance mode is mentioned in the doc shared. However you might see that putting a service or process in Maintenance Mode doesn't take it off of the "Restart All Required" list in Ambari 2.4 which is later addressed as part of the following JIRA in ambari 2.5 Reference: https://issues.apache.org/jira/browse/AMBARI-18450 . ... View more