[
https://issues.apache.org/jira/browse/HDFS-6777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14114478#comment-14114478
]
Hadoop QA commented on HDFS-6777:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12665126/6777-design.2.pdf
against trunk revision d9a7404.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/7840//console
This message is automatically generated.
> 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.2#6252)
