[
https://issues.apache.org/jira/browse/HDFS-13873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16622645#comment-16622645
]
Chen Liang commented on HDFS-13873:
-----------------------------------
[~csun] any updates/plans for this? I saw you are busy with two other Jiras, I
can help on this one if you like :).
Either way, I'm curious about what is the current internal implementation at
Uber? I was syncing with Konstantin, we were planning to do this based on state
id. But the threshold for rejection should probably be based on some runtime
moving average (e.g. the number of txid being processed in past X mins). Any
thoughts on this?
> ObserverNode should reject read requests when it is too far behind.
> -------------------------------------------------------------------
>
> Key: HDFS-13873
> URL: https://issues.apache.org/jira/browse/HDFS-13873
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: hdfs-client, namenode
> Affects Versions: HDFS-12943
> Reporter: Konstantin Shvachko
> Assignee: Chao Sun
> Priority: Major
>
> Add a server-side threshold for ObserverNode to reject read requests when it
> is too far behind.
--
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
