[
https://issues.apache.org/jira/browse/HDFS-13150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17415662#comment-17415662
]
Erik Krogen commented on HDFS-13150:
------------------------------------
[~liutongwei] thanks for sharing your concern!
I don't quite remember how epochs interplay with the durability or reuse of
transaction IDs -- it's been quite a while since I've looked at this area of
the code. Unfortunately I'm also not actively working on HDFS currently. I took
a brief look around the JN code in this area to refresh my memory, but I'm
still missing some details and don't have the time to invest in properly
understanding your concern.
[~shv], do you have any insight on the concern above?
> [Edit Tail Fast Path] Allow SbNN to tail in-progress edits from JN via RPC
> --------------------------------------------------------------------------
>
> Key: HDFS-13150
> URL: https://issues.apache.org/jira/browse/HDFS-13150
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ha, hdfs, journal-node, namenode
> Reporter: Erik Krogen
> Assignee: Erik Krogen
> Priority: Major
> Fix For: HDFS-12943, 3.3.0
>
> Attachments: edit-tailing-fast-path-design-v0.pdf,
> edit-tailing-fast-path-design-v1.pdf, edit-tailing-fast-path-design-v2.pdf
>
>
> In the interest of making coordinated/consistent reads easier to complete
> with low latency, it is advantageous to reduce the time between when a
> transaction is applied on the ANN and when it is applied on the SbNN. We
> propose adding a new "fast path" which can be used to tail edits when low
> latency is desired. We leave the existing tailing logic in place, and fall
> back to this path on startup, recovery, and when the fast path encounters
> unrecoverable errors.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
