[
https://issues.apache.org/jira/browse/HDFS-15119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17421490#comment-17421490
]
Bryan Beaudreault commented on HDFS-15119:
------------------------------------------
Did anything come of the benchmarks [~ahussein]?
Reading through, I agree it would be nice to have a mechanism for refreshing
block locations. But in a low-latency usecase like HBase, ideally that would
happen in the background, not in the critical path of a request. Alternatively,
as mentioned above, one could refresh the locations only in response to certain
exceptions.
> Allow expiration of cached locations in DFSInputStream
> ------------------------------------------------------
>
> Key: HDFS-15119
> URL: https://issues.apache.org/jira/browse/HDFS-15119
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: dfsclient
> Reporter: Ahmed Hussein
> Assignee: Ahmed Hussein
> Priority: Minor
> Fix For: 3.3.0, 3.1.4, 3.2.2
>
> Attachments: HDFS-15119-branch-2.10.003.patch, HDFS-15119.001.patch,
> HDFS-15119.002.patch, HDFS-15119.003.patch
>
>
> Staleness and other transient conditions can affect reads for a long time
> since the block locations may not be re-fetched. It makes sense to make
> cached locations to expire.
> For example, we may not take advantage of local-reads since the nodes are
> blacklisted and have not been updated.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
