[
https://issues.apache.org/jira/browse/HDFS-14998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16983910#comment-16983910
]
Chao Sun commented on HDFS-14998:
---------------------------------
Thanks [~ayushtkn] for sharing your thoughts.
By disabling ZKFC on ObserverNameNodes, we are adding more operational overhead
on users. They need to write extra scripts for the failover, potentially modify
the NameNode startup script, etc. Also, in our environment we have ZKFC alerts
on NameNode hosts, which we have to disable for observers. If we want to enable
dynamic transitions between observer and SBN, we'll also need to enable/disable
this alert dynamically on the hosts, which is not straightforward.
If we allow ZKFC running on Observer, users can pretty much just use the same
operational workflow today for managing NameNodes. Therefore, IMO we should
think whether it is necessary to ask users to do extra work if they want to use
this feature.
> Update Observer Namenode doc for ZKFC after HDFS-14130
> ------------------------------------------------------
>
> Key: HDFS-14998
> URL: https://issues.apache.org/jira/browse/HDFS-14998
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: documentation
> Affects Versions: 3.3.0
> Reporter: Fei Hui
> Assignee: Fei Hui
> Priority: Minor
> Attachments: HDFS-14998.001.patch, HDFS-14998.002.patch,
> HDFS-14998.003.patch
>
>
> After HDFS-14130, we should update observer namenode doc, observer namenode
> can run with ZKFC running
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
