@Abdul Shihab Go to edge node, sudo to hdfs user Get a valid kerberos ticket Run this below command hdfs haadmin -failover [--forceactive] <serviceId> <serviceId>] Example: hdfs haadmin -failover -forceactive namenode1(active) namenode1(standby) If you want to do it from Ambari just restart active namenode, during this process it will make standby as active and after restarted namenode came up it will move to standby but this is not recommended best practice ... View more

@Venkata Sridhar Gangavarapu May I know on which user ambari server installed? root or some other user? If root please add below properties: LINK hadoop.proxyuser.root.groups=* hadoop.proxyuser.root.hosts=* 1. If your cluster is Kerberosed then follow below steps: Go to Hive Service --> Configs --> General and change below property to hive.server2.thrift.sasl.qop = auth-conf Restart all the affected services to make sure changed are set. Then go to Ambari Views server, Manage Ambari --> Hive View --> Setting HiveAuthentication= auth=KERBEROS;principal=hive/_HOST@EXAMPLE.COM;hive.server2.proxy.user=${username};saslQop=auth-conf Let me know if this helps you. ... View more

yarn user does not have access REASON: Tez view was trying to connect to am over port 8088 and did not have enough privileges to access the am. SOLUTION: <property> <name>tez.am.view-acls</name> <value>*</value> <description>AM view ACLs. This setting enables the specified users or groups to view the status of the AM and all DAGs that run within the AM.</description> </property> Now I can see query while executing at the bottom. Issue go fixed. ... View more

Below steps have fixed the issue: 1. If your cluster is Kerberosed then follow below steps: Go to Hive Service --> Configs --> General and change below property to hive.server2.thrift.sasl.qop = auth-conf Restart all the affected services to make sure changed are set. Then go to Ambari Views server, Manage Ambari --> Hive View --> Setting Hive Authentication = auth=KERBEROS;principal=hive/_HOST@EXAMPLE.COM;hive.server2.proxy.user=${username};saslQop=auth-conf 2. If your cluster is not Kerberosed the follow below steps: Go to Hive Service --> Configs --> General and change below property to hive.server2.thrift.sasl.qop = auth Restart all the affected services to make sure changed are set. Then go to Ambari Views server, Manage Ambari --> Hive View --> Setting Hive Authentication = auth=KERBEROS;principal=hive/_HOST@EXAMPLE.COM;hive.server2.proxy.user=${username};saslQop=auth This should fix your above error message issue. ... View more

Below steps has fixed the issue: 1. If your cluster is Kerberosed then follow below steps: Go to Hive Service --> Configs --> General and change below property to hive.server2.thrift.sasl.qop = auth-conf Restart all the affected services to make sure changed are set. Then go to Ambari Views server, Manage Ambari --> Hive View --> Setting Hive Authentication = auth=KERBEROS;principal=hive/_HOST@EXAMPLE.COM;hive.server2.proxy.user=${username};saslQop=auth-conf 2. If your cluster is not Kerberosed the follow below steps: Go to Hive Service --> Configs --> General and change below property to hive.server2.thrift.sasl.qop = auth Restart all the affected services to make sure changed are set. Then go to Ambari Views server, Manage Ambari --> Hive View --> Setting Hive Authentication = auth=KERBEROS;principal=hive/_HOST@EXAMPLE.COM;hive.server2.proxy.user=${username};saslQop=auth This should fix your above error message issue. ... View more