[
https://issues.apache.org/jira/browse/HDFS-13688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16547193#comment-16547193
]
Chen Liang commented on HDFS-13688:
-----------------------------------
Post v001 patch for a Jenkins run. The main difference from WIP.002 patch is
removing the call to ANN for fresh client. Things like handling delegation
token and failover logic handling still need to be added.
I was trying to move {{AlignmentContext}} out of {{DFSClient}}. But it is
actually tricky, because in current patch, msync API in {{ClientProtocol}}
takes state id as argument. So DFSClient must present the state id when making
the call, requiring it to access state id maintained in AlignmentContext.
Haven't come up with a non-hacky alternative. Suggestions are welcome.
> Introduce msync API call
> ------------------------
>
> Key: HDFS-13688
> URL: https://issues.apache.org/jira/browse/HDFS-13688
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Chen Liang
> Assignee: Chen Liang
> Priority: Major
> Attachments: HDFS-13688-HDFS-12943.001.patch,
> HDFS-13688-HDFS-12943.WIP.002.patch, HDFS-13688-HDFS-12943.WIP.patch
>
>
> As mentioned in the design doc in HDFS-12943, to ensure consistent read, we
> need to introduce an RPC call {{msync}}. Specifically, client can issue a
> msync call to Observer node along with a transactionID. The msync will only
> return when the Observer's transactionID has caught up to the given ID. This
> JIRA is to add this API.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
