[jira] [Commented] (HDFS-15664) Prevent Observer NameNode from becoming StandBy NameNode
[ https://issues.apache.org/jira/browse/HDFS-15664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17224985#comment-17224985 ] Aihua Xu commented on HDFS-15664: - Didn't know it was fixed in another place. Thanks [~csun] > Prevent Observer NameNode from becoming StandBy NameNode > > > Key: HDFS-15664 > URL: https://issues.apache.org/jira/browse/HDFS-15664 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: auto-failover >Affects Versions: 2.10.0 >Reporter: Aihua Xu >Assignee: Aihua Xu >Priority: Major > > When the cluster performs a failover from NN1 to NN2, NN2 is asking all the > other NNs to cede active state and transit to StandBy including the Observer > NameNodes. > Seems we should block Observer from becoming StandBy and participating in > Failover. Of course, since we can transit StandBy NameNode to Observer, we > can separately support promote Observer NameNode to StandBy NameNode. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-15664) Prevent Observer NameNode from becoming StandBy NameNode
[ https://issues.apache.org/jira/browse/HDFS-15664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17224933#comment-17224933 ] Chao Sun commented on HDFS-15664: - [~aihuaxu] seems this is already fixed by HDFS-14961? > Prevent Observer NameNode from becoming StandBy NameNode > > > Key: HDFS-15664 > URL: https://issues.apache.org/jira/browse/HDFS-15664 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: auto-failover >Affects Versions: 2.10.0 >Reporter: Aihua Xu >Assignee: Aihua Xu >Priority: Major > > When the cluster performs a failover from NN1 to NN2, NN2 is asking all the > other NNs to cede active state and transit to StandBy including the Observer > NameNodes. > Seems we should block Observer from becoming StandBy and participating in > Failover. Of course, since we can transit StandBy NameNode to Observer, we > can separately support promote Observer NameNode to StandBy NameNode. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Commented] (HDFS-15664) Prevent Observer NameNode from becoming StandBy NameNode
[ https://issues.apache.org/jira/browse/HDFS-15664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17224828#comment-17224828 ] Aihua Xu commented on HDFS-15664: - + [~sunchao] Comments on this? > Prevent Observer NameNode from becoming StandBy NameNode > > > Key: HDFS-15664 > URL: https://issues.apache.org/jira/browse/HDFS-15664 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: auto-failover >Affects Versions: 2.10.0 >Reporter: Aihua Xu >Assignee: Aihua Xu >Priority: Major > > When the cluster performs a failover from NN1 to NN2, NN2 is asking all the > other NNs to cede active state and transit to StandBy including the Observer > NameNodes. > Seems we should block Observer from becoming StandBy and participating in > Failover. Of course, since we can transit StandBy NameNode to Observer, we > can separately support promote Observer NameNode to StandBy NameNode. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
