[ https://issues.apache.org/jira/browse/HDFS-13688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16744299#comment-16744299 ]
Erik Krogen commented on HDFS-13688: ------------------------------------ Hey [~hexiaoqiao], that's a great question. It is definitely on our roadmap to provide a mechanism for clients to use this without requiring application-side changes. We mentioned this in our design document but didn't create a detailed JIRA. I have just done so now at HDFS-14211. Please comment there if you have further questions. > 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 > Fix For: HDFS-12943, 3.3.0 > > Attachments: HDFS-13688-HDFS-12943.001.patch, > HDFS-13688-HDFS-12943.002.patch, HDFS-13688-HDFS-12943.002.patch, > HDFS-13688-HDFS-12943.003.patch, HDFS-13688-HDFS-12943.004.patch, > HDFS-13688-HDFS-12943.005.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