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 "James Thomas (JIRA)" <ji...@apache.org> on 2014/09/07 18:37:29 UTC

[jira] [Updated] (HDFS-6777) Supporting consistent edit log reads when in-progress edit log segments are included

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

James Thomas updated HDFS-6777:
-------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Committed as part of HDFS-6634.

> Supporting consistent edit log reads when in-progress edit log segments are included
> ------------------------------------------------------------------------------------
>
>                 Key: HDFS-6777
>                 URL: https://issues.apache.org/jira/browse/HDFS-6777
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: qjm
>            Reporter: James Thomas
>            Assignee: James Thomas
>         Attachments: 6777-design.2.pdf, 6777-design.pdf, HDFS-6777.patch
>
>
> For inotify, we want to be able to read transactions from in-progress edit log segments so we can serve transactions to listeners soon after they are committed. This JIRA works toward ensuring that we do not send unsync'ed transactions back to the client by 1) discarding in-progress segments if we have a finalized segment starting at the same transaction ID and 2) if there are no finalized segments at the same transaction ID, using only the in-progress segments with the largest seen lastWriterEpoch. See the design document for more background and details.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)