[
https://issues.apache.org/jira/browse/HDFS-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444580#comment-13444580
]
Aaron T. Myers commented on HDFS-3867:
--------------------------------------
I agree that option 1 seems like a better option to me. This also has the nice
side effect of causing the JNs to eagerly rejoin the quorum after just a normal
JN restart. The read fencing, as you mentioned, is also a very desirable side
effect.
Let's go with option #1 for now, and we can revisit option #2 later if
necessary.
> QJM: Support rolling restart of JNs
> -----------------------------------
>
> Key: HDFS-3867
> URL: https://issues.apache.org/jira/browse/HDFS-3867
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ha
> Affects Versions: QuorumJournalManager (HDFS-3077)
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
>
> In order to perform upgrades or other maintenance, it is useful to be able to
> perform a rolling restart of the journal nodes while the NameNode is active.
> Currently, this does not work, because the NN only picks up restarted JNs
> again on the beginning of the next log segment. So, if the NN does not roll
> after each node is restarted in turn, the NN will eventually fail to commit
> to a quorum and crash.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
