[
https://issues.apache.org/jira/browse/HDFS-13880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16607772#comment-16607772
]
Chen Liang commented on HDFS-13880:
-----------------------------------
Thanks for the review [~xkrogen]! All comments addressed, just one note:
{quote} * Why isn't {{getContentSummary}} coordinated?{quote}
The original thought was that, {{getContentSummary}} already yields locks so
could already be returning results based on outdated info. Making it
coordinated seems to have little gain. Also I'm inclined to believe that
chances are users don't expect getContentSummary to be up-to-date anyway. So I
did not make it coordinated, I don't have a strong opinion though.
> Add mechanism to allow certain RPC calls to bypass sync
> -------------------------------------------------------
>
> Key: HDFS-13880
> URL: https://issues.apache.org/jira/browse/HDFS-13880
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: namenode
> Reporter: Chen Liang
> Assignee: Chen Liang
> Priority: Major
> Attachments: HDFS-13880-HDFS-12943.001.patch,
> HDFS-13880-HDFS-12943.002.patch, HDFS-13880-HDFS-12943.003.patch,
> HDFS-13880-HDFS-12943.004.patch
>
>
> Currently, every single call to NameNode will be synced, in the sense that
> NameNode will not process it until state id catches up. But in certain cases,
> we would like to bypass this check and allow the call to return immediately,
> even when the server id is not up to date. One case could be the to-be-added
> new API in HDFS-13749 that request for current state id. Others may include
> calls that do not promise real time responses such as {{getContentSummary}}.
> This Jira is to add the mechanism to allow certain calls to bypass sync.
--
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
