@rajdip chaudhuri You can use Ranger Rest API to be invoked using simple "curl" commands in order to disable/enable various ranger policies. 1. Get the List of Policies using Rest API: http://localhost:6080/service/plugins/policies For example you want to disable the policy ID = 14 (Example "HDFS Global Allow") The do the following: Using Ranger API get the policy data: curl -i -u admin:admin -H "Content-Type: application/json" -X GET http://localhost:6080/service/plugins/policies/14 2. Then you get some JSON output like following: {"id":14,"guid":"eb167192-29a5-490c-9655-8be40c2363eb","isEnabled":true,"createdBy":"Admin","updatedBy":"Admin","createTime":1473764849000,"updateTime":1473764849000,"version":1,"service":"Sandbox_hadoop","name":"HDFS Global Allow","policyType":0,"description":"This policy gives global permission for all users. Disable this to test Apache Ranger","resourceSignature":"6be1f1907223a25472365fea64a3d450","isAuditEnabled":true,"resources":{"path":{"values":["/","/*"],"isExcludes":false,"isRecursive":true}},"policyItems":[{"accesses":[{"type":"read","isAllowed":true},{"type":"write","isAllowed":true},{"type":"execute","isAllowed":true}],"users":[],"groups":["public"],"conditions":[],"delegateAdmin":true}],"denyPolicyItems":[],"allowExceptions":[],"denyExceptions":[],"dataMaskPolicyItems":[],"rowFilterPolicyItems":[]} Notice it has ["isEnabled":true] 3. Now Paste the output to a file "/tmp/14.json", then change it to ["isEnabled":false] and then PUT the data using curl. Content of "14.json" file as following: {"id":14,"guid":"eb167192-29a5-490c-9655-8be40c2363eb","isEnabled":false,"createdBy":"Admin","updatedBy":"Admin","createTime":1473764849000,"updateTime":1473764849000,"version":1,"service":"Sandbox_hadoop","name":"HDFS Global Allow","policyType":0,"description":"This policy gives global permission for all users. Disable this to test Apache Ranger","resourceSignature":"6be1f1907223a25472365fea64a3d450","isAuditEnabled":true,"resources":{"path":{"values":["/","/*"],"isExcludes":false,"isRecursive":true}},"policyItems":[{"accesses":[{"type":"read","isAllowed":true},{"type":"write","isAllowed":true},{"type":"execute","isAllowed":true}],"users":[],"groups":["public"],"conditions":[],"delegateAdmin":true}],"denyPolicyItems":[],"allowExceptions":[],"denyExceptions":[],"dataMaskPolicyItems":[],"rowFilterPolicyItems":[]} 4. Now run the following curl command: curl -i -u admin:admin -H "Content-Type: application/json" -X PUT -d@/tmp/14.json http://localhost:6080/service/plugins/policies/14 More details: https://cwiki.apache.org/confluence/display/RANGER/REST+APIs+for+Policy+Management . ... View more

@shi cheng I will try to change the "1.1.0-SNAPSHOT" from file : https://github.com/apache/ambari/blob/trunk/ambari-metrics/ambari-metrics-storm-sink/pom.xml#L33-L35 <properties> <storm.version>1.1.0-SNAPSHOT</storm.version> </properties> . Try changing the "1.1.0-SNAPSHOT" to "1.1.0" as i see that this is available in the repo: http://repo.hortonworks.com/content/groups/public/org/apache/storm/storm-core/1.1.0/ Looks like the storm support was added from ambari 2.4 recently [1] and now the 1.1.0-SNAPSHOT is not present in the repo so try changing it to 1.1.0 [1] https://issues.apache.org/jira/browse/AMBARI-17080 [2] https://github.com/apache/ambari/commit/57fccc039c00b301836cf74c15016734fedd64ca (Search for 1.1.0-SNAPSHOT) . ... View more

@Banshidhar Sahoo Please see the release notes of ambari 2.5.0.3 it is recently released and supported. http://docs.hortonworks.com/HDPDocuments/Ambari-2.5.0.3/bk_ambari-release-notes/content/ch_relnotes-ambari-2.5.0.3.html . You can also find the ambari support matrices here: http://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.6.0/bk_support-matrices/content/ch_matrices-ambari.html ... View more

@Rahul Jain In your error stack i see the following entry: Host registration aborted. Ambari Agent host cannot reach Ambari Server 'ns2.dns2go.com:8080'. Please check the network connectivity between the Ambari Agent host and the Ambari Server . Can you please make sure that the hostnames are correctly used and every agent host machine and ambari host machine is returning the correct hostname (FQDN) in the following commands output? # hostname -f . From the ambari agent machine try to access the ambari server's 8080 port to see if there is no firewall restriction. # telnet ns2.dns2go.com 8080 - If you are not able to connect then there may be a firewall or Network issue between the ambari server & agent machine. If IP Tables is enabled on ambari then try disabling it. - Make sue that the "/etc/hosts" file of ambari agent hosts as well as ambari server has the entries of all the cluster members in it. Example: following kind of entries exist on every cluster member machine so that they can resolve each other. 10.10.20.120 ns2.dns2go.com 10.10.20.130 agent1.dns2go.com 10.10.20.140 agent2.dns2go.com 10.10.20.150 agent3.dns2go.com . ... View more