hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3862) QJM: don't require a fencer to be configured if shared storage has built-in single-writer semantics
Date Sun, 03 May 2015 11:49:06 GMT

    [ https://issues.apache.org/jira/browse/HDFS-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14525787#comment-14525787
] 

Hadoop QA commented on HDFS-3862:
---------------------------------

(!) The patch artifact directory has been removed! 
This is a fatal error for test-patch.sh.  Aborting. 
Jenkins (node H4) information at https://builds.apache.org/job/PreCommit-HDFS-Build/10738/
may provide some hints.

> 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, HDFS-3862.002.patch, HDFS-3862.003.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.3.4#6332)

Mime
View raw message