ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jayush Luniya (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-10067) ZKFailoverController failed on restart
Date Fri, 13 Mar 2015 20:46:39 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-10067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jayush Luniya updated AMBARI-10067:
-----------------------------------
    Attachment: AMBARI-10067.patch

> ZKFailoverController failed on restart
> --------------------------------------
>
>                 Key: AMBARI-10067
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10067
>             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
state.
> 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
(v6.3.4#6332)

Mime
View raw message