hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erik Krogen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-13872) Only ClientProtocol should perform msync wait
Date Mon, 27 Aug 2018 22:24:00 GMT

    [ https://issues.apache.org/jira/browse/HDFS-13872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16594288#comment-16594288

Erik Krogen commented on HDFS-13872:

[~vagarychen], [~shv], thoughts?

> 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
>            Priority: Major
> 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

This message was sent by Atlassian JIRA

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

View raw message