You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Erik Krogen (JIRA)" <ji...@apache.org> on 2018/08/27 22:23:00 UTC

[jira] [Created] (HDFS-13872) Only ClientProtocol should perform msync wait

Erik Krogen created HDFS-13872:
----------------------------------

             Summary: Only ClientProtocol should perform msync wait
                 Key: HDFS-13872
                 URL: https://issues.apache.org/jira/browse/HDFS-13872
             Project: Hadoop HDFS
          Issue Type: Sub-task
            Reporter: Erik Krogen


Currently the implementation of msync added in HDFS-13767 waits until the server has caught up to the client-specified transaction ID regardless of what the inbound RPC is. This particularly causes problems for ObserverReadProxyProvider (see HDFS-13779) when we try to fetch the state from an observer/standby; this should be a quick operation, but it has to wait for the node to catch up to the most current state. I initially thought all {{HAServiceProtocol}} methods should thus be excluded from the wait period, but actually I think the right approach is that _only_ {{ClientProtocol}} methods should be subjected to the wait period. I propose that we can do this via an annotation on client protocol which can then be checked within {{ipc.Server}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org