[jira] [Updated] (IMPALA-8126) Move per-host resource utilization counters to per-host profiles in coordinator

["Joe McDonnell (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IMPALA-8126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joe McDonnell updated IMPALA-8126:
----------------------------------
    Target Version: Impala 4.0  (was: Impala 3.4.0)

> Move per-host resource utilization counters to per-host profiles in coordinator
> -------------------------------------------------------------------------------
>
>                 Key: IMPALA-8126
>                 URL: https://issues.apache.org/jira/browse/IMPALA-8126
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Backend
>    Affects Versions: Impala 3.2.0
>            Reporter: Lars Volker
>            Priority: Major
>              Labels: observability, profile, supportability
>
> Once IMPALA-7694 gets in we should move the per-host resource utilization counters in {{Coordinator::ComputeQuerySummary()}} to the host profiles in {{Coordinator::BackendState}}.
> [~tarmstrong] pointed out [here|https://gerrit.cloudera.org/#/c/12069/13/be/src/runtime/coordinator.cc@789]:
> {quote}
> We could also simplify BackendState::ComputeResourceUtilization() to just use the per-backend counters instead of iterating over fragments.
> I think there may be some compatibility concerns about removing these - existence of the counters isn't contractual but we don't want to break useful tools if avoidable.
> For example, I confirmed that Cloudera Manager actually does parse the existing strings (which is a little sad, but understandable given the lack of other counters).
> {quote}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org