You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Yi Liu (JIRA)" <ji...@apache.org> on 2014/08/17 11:02:18 UTC

[jira] [Updated] (HDFS-3862) QJM: don't require a fencer to be configured if shared storage has built-in single-writer semantics

     [ https://issues.apache.org/jira/browse/HDFS-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yi Liu updated HDFS-3862:
-------------------------

    Attachment: HDFS-3862.001.patch

The patch adds a new API to JournalManager: {{boolean isNativelySingleWriter();}}
And hanle following cases:
* if the shared storage has built-in single-write semantics, then user *is not forced* to specify a fencer.
* if #1, but a forcer is configured, then ZKFC will do forcing as original logic; but if forcing is failed, it’s ignored with warning log. Failover will continue.
* if #1, but a bad forcer is configured, then forcer is ignored with warning log. Failover will continue.
* if specify “forcefence” option for failover when using DFSHAAdmin, then a forcer should be configured even if #1


> QJM: don't require a fencer to be configured if shared storage has built-in single-writer semantics
> ---------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-3862
>                 URL: https://issues.apache.org/jira/browse/HDFS-3862
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: ha
>    Affects Versions: QuorumJournalManager (HDFS-3077)
>            Reporter: Todd Lipcon
>            Assignee: Yi Liu
>         Attachments: HDFS-3862.001.patch
>
>
> Currently, NN HA requires that the administrator configure a fencing method to ensure that only a single NameNode may write to the shared storage at a time. Some shared edits storage implementations (like QJM) inherently enforce single-writer semantics at the storage level, and thus the user should not be forced to specify one.
> We should extend the JournalManager interface so that the HA code can operate without a configured fencer if the JM has such built-in fencing.



--
This message was sent by Atlassian JIRA
(v6.2#6252)