[
https://issues.apache.org/jira/browse/HDFS-12977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16370481#comment-16370481
]
Plamen Jeliazkov commented on HDFS-12977:
-----------------------------------------
Thanks for taking a look Konstantin.
With regards to #1 – If I try to do that right away I would have to import the
hdfs module into common. Perhaps I can find a smarter way around that though.
May require changing the constructor for Call though.
And with #2 – that changes the logic to fetch the EditLog's Txid without the
writeLock. As long as this is called after the response is created I think we
are OK but I am not sure how this will work out with async EditLog feature. We
don't want to end up in a situation where the client gets a response with a
Txid that is actually behind what it's requsts's/response's Txid is.
> Add stateId to RPC headers.
> ---------------------------
>
> Key: HDFS-12977
> URL: https://issues.apache.org/jira/browse/HDFS-12977
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ipc, namenode
> Reporter: Konstantin Shvachko
> Assignee: Plamen Jeliazkov
> Priority: Major
> Attachments: HDFS_12977.trunk.001.patch
>
>
> stateId is a new field in the RPC headers of NameNode proto calls.
> stateId is the journal transaction Id, which represents LastSeenId for the
> clients and LastWrittenId for NameNodes. See more in [reads from Standby
> design
> doc|https://issues.apache.org/jira/secure/attachment/12902925/ConsistentReadsFromStandbyNode.pdf].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
