@Himani Bansal It can be done using Ambari UI or API calls. https://docs.hortonworks.com/HDPDocuments/Ambari-2.6.2.0/bk_ambari-operations/content/rolling_restarts.html https://docs.hortonworks.com/HDPDocuments/Ambari-2.6.2.0/bk_ambari-operations/content/setting_rolling_restart_parameters.html API calls: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=41812517 ... View more

@Geoffrey Shelton Okot Only a user who own the thread Or a user with 1000+ points can accept other users answers as accepted. I have marked your previous answer as "Accepted" which you answered on "Aug 09, 2017" as that answer looks more informative form this HCC thread perspective. ... View more

@Marek Martofel Wonderful!!! thank you for sharing so detailed steps. I am marking this thread as answered. ... View more

@Marek Martofel So basically you should do the following: 1. Setup truststore for Ambari Server : (option-4) # ambari-server setup-seturity [4] Setup truststore 2. Import Ranger certificate inside the ambari truststore it can also be done manually or using the following option (option-5) # ambari-server setup-seturity [5] Import certificate to truststore. . ... View more

@Marek Martofel Can you please check if you have setup Abari Truststore? Do you see any 'truststore' related settings in your current or old "/etc/ambari-server/conf/ambari.properties" ? # grep 'trust' /etc/ambari-server/conf/ambari.properties # grep 'trust' /etc/ambari-server/conf/ambari.properties.rpmsave Based on the error it looks like Your Ranger UI is running on HTTPs and ambari truststore does not have the Ranger certificate imported to it. You can refer to the following doc to know more about Setting up Truststore for Ambari : https://docs.hortonworks.com/HDPDocuments/Ambari-2.6.2.2/bk_ambari-security/content/set_up_truststore_for_ambari_server.html . The following HCC article also explains the cause and remedy of "Truststore path or password is not set" https://community.hortonworks.com/articles/39865/enabling-https-for-ambariserver-and-troubleshootin.html ... View more

@Ayoub Bounfour Exception in thread "main" java.lang.IllegalArgumentException: A HostProvider may not be empty! The above error that you reported is coming from The "StaticHostProvider.java" class. which has the following code: https://github.com/apache/zookeeper/blob/release-3.4.6/src/java/main/org/apache/zookeeper/client/StaticHostProvider.java#L72-L86 this.serverAddresses.add( new InetSocketAddress(InetAddress.getByAddress( address.getHostName(), resolvedAddress.getAddress()), address.getPort())); } else { this.serverAddresses.add(new InetSocketAddress(resolvedAddress.getHostAddress(), address.getPort())); } } } if (this.serverAddresses.isEmpty()) { throw new IllegalArgumentException( "A HostProvider may not be empty!"); } . So somehoiw the FQDN (hostname) of your Zookeeper host is not correct. So can you please check if you are specifying the IP Adderss/Hostname in your configs? Also please verify the following command on your cluster nodes to verify if the FQDN (fully qualified Hostname) is correctly setup? Also please chekc that every host is resolving each other using their hostnmae. # hostname -f # cat /etc/hosts . ... View more