[
https://issues.apache.org/jira/browse/IMPALA-8209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16773562#comment-16773562
]
ASF subversion and git services commented on IMPALA-8209:
---------------------------------------------------------
Commit 257fa0c68bb4e64880a64844d8d4023c54645230 in impala's branch
refs/heads/master from Lars Volker
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=257fa0c ]
IMPALA-8209: Include fragment instance ID in memz/ breakdown
The change for IMPALA-7694 had accidentally removed the fragment
instance ID from the memz/ breakdown. This change puts it back and adds
a test to make sure it's there.
This change also pads query IDs with zeros when printing them in the
backend.
Change-Id: I73bf06bf95c88186b16fd03243de9bac946c5cc8
Reviewed-on: http://gerrit.cloudera.org:8080/12524
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Fragment instance ID no longer displayed on /memz
> -------------------------------------------------
>
> Key: IMPALA-8209
> URL: https://issues.apache.org/jira/browse/IMPALA-8209
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 3.2.0
> Reporter: Lars Volker
> Assignee: Lars Volker
> Priority: Major
> Labels: observability
> Fix For: Impala 3.2.0
>
>
> The change for IMPALA-7694 dropped the fragment instance ID from the
> runtime-state profile. However, this also removed it from the /memz page. We
> should add it back there.
> https://gerrit.cloudera.org/#/c/12069/8/be/src/runtime/runtime-state.cc@76
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
