You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Yusaku Sako (JIRA)" <ji...@apache.org> on 2017/03/20 21:51:41 UTC
[jira] [Updated] (AMBARI-19261) AMS cannot start after NN HA is
enabled due to hbase.rootdir pointing to Standby NN
[ https://issues.apache.org/jira/browse/AMBARI-19261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yusaku Sako updated AMBARI-19261:
---------------------------------
Reporter: Sviatoslav Tereshchenko (was: Aravindan Vijayan)
> AMS cannot start after NN HA is enabled due to hbase.rootdir pointing to Standby NN
> -----------------------------------------------------------------------------------
>
> Key: AMBARI-19261
> URL: https://issues.apache.org/jira/browse/AMBARI-19261
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
> Affects Versions: 2.5.0
> Reporter: Sviatoslav Tereshchenko
> Assignee: Aravindan Vijayan
> Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19261-2.patch, AMBARI-19261.patch
>
>
> BUG
> Stack advisor never updates the hbase.rootdir for NN HA deployment.
> So AMS was pointing to standby NN instead of nameservice resulting in :
> {code}
> 2016-12-20 21:43:41,406 WARN [natd77-ipvs-upg-sanity-2220-5:61300.activeMasterManager] retry.RetryInvocationHandler: Exception while invoking ClientNamenodeProtocolTranslatorPB.setSafeMode over null. Not retrying because try once and fail.
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.ipc.StandbyException): Operation category READ is not supported in state standby
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)