[
https://issues.apache.org/jira/browse/HDFS-6777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Thomas updated HDFS-6777:
-------------------------------
Description: 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 discarding in-progress segments if
we have a finalized segment starting at the same transaction ID. See the design
document for more background and details. (was: 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.)
> 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
> Fix For: 2.6.0
>
> 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 discarding in-progress segments if we have
> a finalized segment starting at the same transaction ID. See the design
> document for more background and details.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
