[
https://issues.apache.org/jira/browse/AMBARI-12488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14636086#comment-14636086
]
Hadoop QA commented on AMBARI-12488:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12746441/AMBARI-12488.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/3437//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3437//console
This message is automatically generated.
> RU - Use haadmin failover command instead of killing ZKFC during
> upgrade/downgrade
> ----------------------------------------------------------------------------------
>
> Key: AMBARI-12488
> URL: https://issues.apache.org/jira/browse/AMBARI-12488
> Project: Ambari
> Issue Type: Story
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Alejandro Fernandez
> Assignee: Alejandro Fernandez
> Labels: rolling_upgrade
> Fix For: 2.1.2
>
> Attachments: AMBARI-12488.branch-2.1.2.patch, AMBARI-12488.patch
>
>
> Currently RU orchestration during upgrade/downgrade kills ZKFC on the active
> NameNode to initiate a failover to standby. We should instead use the
> failover command.
> E.g.,
> {code}
> su hdfs -c 'hdfs haadmin -failover nn1 nn2'
> {code}
> Where nn1 is the current namenode if it if the active one, and nn2 is the
> remaining namenode.
> This is safer than killing zkfc on the active namenode because this command
> first tries to gracefully transition a NameNode to the Standby state. If this
> fails, the fencing methods (as configured by dfs.ha.fencing.methods) will be
> attempted until one succeeds. After this process the second NameNode will be
> transitioned to the Active state.
> It reduces long waits between ZKFC kill, failure kicking-in after a timeout,
> and then NN becoming active.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
