[
https://issues.apache.org/jira/browse/HDFS-13767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16559149#comment-16559149
]
Konstantin Shvachko commented on HDFS-13767:
--------------------------------------------
I like the approach. Don't think preserving the ordering is needed. Seems you
need to put some more work to complete this.
May be changing {{receiveRequestState(header)}} to return {{clientStateId}}, so
that you could pass it into {{RpcCall}}, which is then retrieved in
{{Handler.run()}} to verify if the SBN already caught up. BTW you can also
incorporate the {{AC.isAlwaysRecent()}} logic inside {{receiveRequestState()}}
instead of adding new method.
> Add msync server implementation.
> --------------------------------
>
> Key: HDFS-13767
> URL: https://issues.apache.org/jira/browse/HDFS-13767
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: namenode
> Reporter: Chen Liang
> Assignee: Chen Liang
> Priority: Major
> Attachments: HDFS-13767.WIP.001.patch, HDFS-13767.WIP.002.patch
>
>
> This is a followup on HDFS-13688, where msync API is introduced to
> {{ClientProtocol}} but the server side implementation is missing. This is
> Jira is to implement the server side logic.
--
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
