[
https://issues.apache.org/jira/browse/IMPALA-7819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong resolved IMPALA-7819.
-----------------------------------
Resolution: Fixed
Fix Version/s: Impala 3.2.0
> Scanners should include "storage wait time" per scan node
> ---------------------------------------------------------
>
> Key: IMPALA-7819
> URL: https://issues.apache.org/jira/browse/IMPALA-7819
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Reporter: Tim Armstrong
> Assignee: Tim Armstrong
> Priority: Major
> Fix For: Impala 3.2.0
>
>
> We have TotalStorageWaitTime per fragment instance, which aggregates various
> things like times spent waiting for the I/O manager and time spent in the
> Kudu client. This is useful but often we want to understand why a specific
> scan is slow. This is tricky because TotalStorageWaitTime and the various
> scanner thread timers in the profile are in different subsections and don't
> measure comparable things if there are multiple scans in the profile.
> We should also include this timings in the scan profile to address this.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
