@Rafael Gomez Additionally, we see that you are getting the following error: Unable to connect to: https://hadoop-m:8441/agent/v1/register/hadoop-m.c.hdp-1-163209.internal Which indicates either you have not setup the Hostname for all your ambari agent hosts properly or they are not able to communicate to ambari server on the mentioned ports. So please check if from the ambari agent machines you are able to access the below mentioned port of ambari server? # telnet hadoop-m 8441 # telnet hadoop-m 8440 . Also every host in the cluster should be configured with a proper FQDN/hostname so please check if you have the proper entry inside the /etc/hosts file inside every ambari agent machine. Also they should return proper FQDN when you run the following command on ambari-agent hosts: # hostname -f . Also pleas echeck from ambari agent machine if you are able to connect to ambari server using openssl command and able to see the certificate of ambari server? # openssl s_client -connect hadoop-m:8440 -tls1_2 OR # openssl s_client -connect hadoop-m:8440 AND # openssl s_client -connect hadoop-m:8441 -tls1_2 OR # openssl s_client -connect hadoop-m:8441 . ... View more

@Rafael Gomez The issue that you are afcing indicates Ambari DB Corruption. As we see that /request URL itslef is throwing NullPointerException so it will not be able to process any further request. 15 May 2017 07:16:14,016 WARN [qtp-ambari-client-26] ServletHandler:563 - /api/v1/clusters/hadoop/requests java.lang.NullPointerException . If you started noticing this issue happening after installing HUE service then please delete the HUE service from ambari Database completely by running the following queries on Ambari DB and then restart ambari server to see if it fixes your issue. delete from hostcomponentstate where service_name = 'HUE'; delete from hostcomponentdesiredstate where service_name = 'HUE'; delete from servicecomponentdesiredstate where service_name = 'HUE'; delete from servicedesiredstate where service_name = 'HUE'; delete from serviceconfighosts where service_config_id in (select service_config_id from serviceconfig where service_name = 'HUE'); delete from serviceconfigmapping where service_config_id in (select service_config_id from serviceconfig where service_name = 'HUE'); delete from serviceconfig where service_name = 'HUE'; delete from requestresourcefilter where service_name = 'HUE'; delete from requestoperationlevel where service_name = 'HUE'; delete from clusterservices where service_name ='HUE'; delete from clusterconfig where type_name like 'hue%'; delete from clusterconfigmapping where type_name like 'hue%'; . NOTE: Please take a Ambari Database Dump before manipulating the Ambari DB. ... View more

@Zhao Chaofeng Can you please share the exact command that you are using for consumer and producer? Also do you see any issue when you append the following option to your Kafka Producer/Consumer? --security-protocol SASL_PLAINTEXT . Also if you have set "security.inter.broker.protocol" then what is the value for this property? . ... View more

@Sushant Choudhary Granting permission is not different for Hive/Tez/File View or other Views. The curl call should be almost same. You need to just adjust the privilleges properly in the json. Please take a look at the "Hive View" granting example for user "jay" Example For Hive curl -i -u admin:admin -H "X-Requested-By: ambari" -X PUT -d '[{"PrivilegeInfo":{"permission_name":"VIEW.USER","principal_name":"amy_ds","principal_type":"USER"}},{"PrivilegeInfo":{"permission_name":"VIEW.USER","principal_name":"holger_gov","principal_type":"USER"}},{"PrivilegeInfo":{"permission_name":"VIEW.USER","principal_name":"maria_dev","principal_type":"USER"}},{"PrivilegeInfo":{"permission_name":"VIEW.USER","principal_name":"raj_ops","principal_type":"USER"}},{"PrivilegeInfo":{"permission_name":"VIEW.USER","principal_name":"jay","principal_type":"USER"}},{"PrivilegeInfo":{"permission_name":"VIEW.USER","principal_name":"CLUSTER.ADMINISTRATOR","principal_type":"ROLE"}}]' http://localhost:8080/api/v1/views/HIVE/versions/1.5.0/instances/AUTO_HIVE_INSTANCE/privileges For more information of User Permissions for views please refer to: - https://docs.hortonworks.com/HDPDocuments/Ambari-2.4.2.0/bk_ambari-views/content/section_user_permissions_hive_view.html - https://docs.hortonworks.com/HDPDocuments/Ambari-2.4.2.0/bk_ambari-views/content/section_user_permissions_tez_view.html ... View more

@Sushant Choudhary From readability point i am posting the JSON data in the Pretty JSON format here. [ { "PrivilegeInfo": { "permission_name": "VIEW.USER", "principal_name": "amy_ds", "principal_type": "USER" } }, { "PrivilegeInfo": { "permission_name": "VIEW.USER", "principal_name": "holger_gov", "principal_type": "USER" } }, { "PrivilegeInfo": { "permission_name": "VIEW.USER", "principal_name": "maria_dev", "principal_type": "USER" } }, { "PrivilegeInfo": { "permission_name": "VIEW.USER", "principal_name": "raj_ops", "principal_type": "USER" } }, { "PrivilegeInfo": { "permission_name": "VIEW.USER", "principal_name": "jay", "principal_type": "USER" } }, { "PrivilegeInfo": { "permission_name": "VIEW.USER", "principal_name": "views", "principal_type": "GROUP" } }, { "PrivilegeInfo": { "permission_name": "VIEW.USER", "principal_name": "CLUSTER.ADMINISTRATOR", "principal_type": "ROLE" } }, { "PrivilegeInfo": { "permission_name": "VIEW.USER", "principal_name": "CLUSTER.OPERATOR", "principal_type": "ROLE" } }, { "PrivilegeInfo": { "permission_name": "VIEW.USER", "principal_name": "SERVICE.OPERATOR", "principal_type": "ROLE" } }, { "PrivilegeInfo": { "permission_name": "VIEW.USER", "principal_name": "SERVICE.ADMINISTRATOR", "principal_type": "ROLE" } }, { "PrivilegeInfo": { "permission_name": "VIEW.USER", "principal_name": "CLUSTER.USER", "principal_type": "ROLE" } } . You can edit the PrivilegeInfo section from the above JSON data to give appropriate permission (principal_name) . ... View more

@Saurabh Agree, I have report it to : https://issues.apache.org/jira/browse/AMBARI-21007 ... View more

@Saurabh Please check if your Atlas Service is running fine on port 21000 on localhost? # netstat -tnlpa | grep 21000 . Also do you see any ERROR/ Warning on atlas log? # less /var/log/atlas/atlas.20170419-185147.err # less /var/log/atlas/atlas.20170419-185147.out . ... View more