[
https://issues.apache.org/jira/browse/IMPALA-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong resolved IMPALA-1644.
-----------------------------------
Resolution: Won't Fix
The benefit for the complexity seems limited, since this only really comes into
play if block locations are stale. It could be mitigated more if we enable the
remote data and file handle caches too.
> Move scan ranges for unexpected remote reads to the remote read disk queue
> --------------------------------------------------------------------------
>
> Key: IMPALA-1644
> URL: https://issues.apache.org/jira/browse/IMPALA-1644
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Affects Versions: Impala 2.0
> Reporter: Matthew Jacobs
> Priority: Minor
> Labels: performance
>
> Move scan ranges for remote reads to a special remote read disk queue.
> This would help avoid hammering the cluster with remote reads when metadata
> becomes outdated.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
