hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brahma Reddy Battula (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-8161) Both Namenodes are in standby State
Date Fri, 24 Apr 2015 02:30:39 GMT

    [ https://issues.apache.org/jira/browse/HDFS-8161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14510368#comment-14510368
] 

Brahma Reddy Battula commented on HDFS-8161:
--------------------------------------------

As session id got corrupted and ZKFC received different session id ( described in  ZOOKEEPER-2175
)..It's not able to get the lock on {{/hadoop-ha/hacluster/ActiveStandbyElectorLock}} .. Hence
both ZKFC's are not able got lock, both NN's are in standby..

Raised issue in ZK community for checksum validation.

> Both Namenodes are in standby State
> -----------------------------------
>
>                 Key: HDFS-8161
>                 URL: https://issues.apache.org/jira/browse/HDFS-8161
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: auto-failover
>    Affects Versions: 2.6.0
>            Reporter: Brahma Reddy Battula
>            Assignee: Brahma Reddy Battula
>         Attachments: ACTIVEBreadcumb and StandbyElector.txt
>
>
> Suspected Scenario:
> ================
> Start cluster with three Nodes.
> Reboot Machine where ZKFC is not running..( Here Active Node ZKFC should open session
with this ZK )
> Now  ZKFC ( Active NN's ) session expire and try re-establish connection with another
ZK...Bythe time  ZKFC ( StndBy NN's ) will try to fence old active and create the active Breadcrumb
and Makes SNN to active state..
> But immediately it fence to standby state.. ( Here is the doubt)
> Hence both will be in standby state..



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

Mime
View raw message