You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Tao Jie (JIRA)" <ji...@apache.org> on 2015/11/13 09:48:10 UTC

[jira] [Created] (HADOOP-12569) ZKFC should stop namenode before itself quit in some circumstances

Tao Jie created HADOOP-12569:
--------------------------------

             Summary: ZKFC should stop namenode before itself quit in some circumstances
                 Key: HADOOP-12569
                 URL: https://issues.apache.org/jira/browse/HADOOP-12569
             Project: Hadoop Common
          Issue Type: Bug
          Components: ha
    Affects Versions: 2.6.0
            Reporter: Tao Jie


We have met such a HA scenario:
NN1(active) and zkfc1 on node1;
NN2(standby) and zkfc2 on node2.
1,Stop network on node1, NN2 becomes active. On node2, zkfc2 kills itself since it cannot connect to zookeeper, but leaving NN1 still running.
2,Several minutes later, network on node1 recovers. NN1 is running but out of control. NN1 and NN2 both run as active nn.
Maybe zkfc should stop nn before quit in such circumstances.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)