hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colin Patrick McCabe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-5459) fix bootstrapStandby race condition introduced in HDFS-5080
Date Tue, 05 Nov 2013 01:00:56 GMT

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

Colin Patrick McCabe updated HDFS-5459:
---------------------------------------

    Priority: Minor  (was: Major)

I am reducing this to minor, since the ill effect is that you believe that the JN can start
up after the bootstrapStandby, when in fact it can't.

It does not cause data corruption of any kind.

> fix bootstrapStandby race condition introduced in HDFS-5080
> -----------------------------------------------------------
>
>                 Key: HDFS-5459
>                 URL: https://issues.apache.org/jira/browse/HDFS-5459
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: qjm
>    Affects Versions: 2.2.0
>            Reporter: Colin Patrick McCabe
>            Priority: Minor
>
> In HDFS-5080, we added the ability to fetch the in-progress edit log from {{JournalNodes}}.
 However, in some cases, {{BootstrapStandby}} can now fetch entries that have not made it
to a quorum of nodes, since we used lastWrittenTxid rather than the last committed txid. 
We should fix this race condition.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message