[
https://issues.apache.org/jira/browse/HDFS-14067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16685956#comment-16685956
]
Chao Sun commented on HDFS-14067:
---------------------------------
bq. Chao, I was going to say that the .000 patch only fixes client and does not
address the server-side check but it is sounding like this JIRA is tending
towards a "Won't Fix".
Good find [~zero45]. Will keep this in mind in case we'll do another patch.
bq. Yes keeping Observer as Standby in ZK is incorrect. Can we change the state
in ZK for Observer? We now can change state from Standby to Active and vice
versa. Should we be able to change it the same way for Standby to/from Observer
transitions?
Currently the active/standby status in ZK is managed by watching the ZK lock,
I'm not sure how observer can fit into this picture. To populate the observer
state into ZK, we'll need to change the {{ZKFCProtocol}} and use that in
{{transitionToObserver}}.
> Allow manual failover between standby and observer
> --------------------------------------------------
>
> Key: HDFS-14067
> URL: https://issues.apache.org/jira/browse/HDFS-14067
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Chao Sun
> Assignee: Chao Sun
> Priority: Major
> Attachments: HDFS-14067-HDFS-12943.000.patch
>
>
> Currently if automatic failover is enabled in a HA environment, transition
> from standby to observer would be blocked:
> {code}
> [hdfs@*** hadoop-3.3.0-SNAPSHOT]$ bin/hdfs haadmin -transitionToObserver ha2
> Automatic failover is enabled for NameNode at ****
> Refusing to manually manage HA state, since it may cause
> a split-brain scenario or other incorrect state.
> If you are very sure you know what you are doing, please
> specify the --forcemanual flag.
> {code}
> We should allow manual transition between standby and observer in this case.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
