[
https://issues.apache.org/jira/browse/HDFS-10702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16181648#comment-16181648
]
Sean Mackrory commented on HDFS-10702:
--------------------------------------
I was just chatting with [~yzhangal] about this feature and he had a cool
suggestion: a configuration that eliminates any need for code changes in an
application to use this. I see 2 options here:
- a configuration that causes the minimum transaction ID to be set at 0 by
default (i.e. just trust that the standby NN's are already sufficiently up to
date)
- a configuration that triggers the HDFS client retrieving the latest
transaction ID and setting it as the minimum, so that results are at least as
fresh as the client itself.
> Add a Client API and Proxy Provider to enable stale read from Standby
> ---------------------------------------------------------------------
>
> Key: HDFS-10702
> URL: https://issues.apache.org/jira/browse/HDFS-10702
> Project: Hadoop HDFS
> Issue Type: New Feature
> Reporter: Jiayi Zhou
> Assignee: Sean Mackrory
> Priority: Minor
> Attachments: HDFS-10702.001.patch, HDFS-10702.002.patch,
> HDFS-10702.003.patch, HDFS-10702.004.patch, HDFS-10702.005.patch,
> HDFS-10702.006.patch, HDFS-10702.007.patch, HDFS-10702.008.patch,
> StaleReadfromStandbyNN.pdf
>
>
> Currently, clients must always talk to the active NameNode when performing
> any metadata operation, which means active NameNode could be a bottleneck for
> scalability. One way to solve this problem is to send read-only operations to
> Standby NameNode. The disadvantage is that it might be a stale read.
> Here, I'm thinking of adding a Client API to enable/disable stale read from
> Standby which gives Client the power to set the staleness restriction.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
