[
https://issues.apache.org/jira/browse/HDFS-13873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626547#comment-16626547
]
Chen Liang commented on HDFS-13873:
-----------------------------------
Update here for reference: Synced offline with Konstantin. Seems one
fundamental issue with my previous proposed approaches is that, when the server
state id increment is slow, it is hard to differentiate between: 1. the server
is slow; 2. there were not many write anyway. Meaning, in addition to
estimating request syncing time, we also need to have a reasonable estimate of
server state catch up rate, instead purely based current window.
> 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
