ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <>
Subject [jira] [Commented] (AMBARI-10067) ZKFailoverController failed on restart
Date Sat, 14 Mar 2015 00:05:38 GMT


Hudson commented on AMBARI-10067:

SUCCESS: Integrated in Ambari-trunk-Commit #2031 (See [])
AMBARI-10067: ZKFailoverController failed on restart (jluniya) (jluniya:
* ambari-server/src/main/resources/common-services/HDFS/
* ambari-server/src/test/python/stacks/2.0.6/HDFS/
* ambari-server/src/main/resources/common-services/HDFS/

> ZKFailoverController failed on restart
> --------------------------------------
>                 Key: AMBARI-10067
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-agent
>    Affects Versions: 2.0.0
>            Reporter: Jayush Luniya
>            Assignee: Jayush Luniya
>             Fix For: 2.0.0
>         Attachments: AMBARI-10067.patch
> Issue Summary:
> 1. When Namenode HA is enabled and "automatic failover" is selected, the "hdfs zkfc -formatZK"
command is used to create a znode in ZooKeeper inside of which the automatic failover system
stores its data.
> 2. When Namenode HA is enabled through the wizard, the user is asked to manually run
this command. 
> 3. When Namenode HA cluster is deployed using HA blueprint, the agent script has been
executing "hdfs zkfc -formatZK -force -nonInteractive" to auto-format the znode. This means
that everytime a ZKFC starts, we end up formatting the znode used to maintain the failover
> Fix:
> 1. Changing the command to "hdfs zkfc -formatZK -nonInteractive" so that the failover
state is not reformatted and handling the case when the command returns a status=2 to indicate
that the znode already exists and hence skipping formatting it.

This message was sent by Atlassian JIRA

View raw message