[
https://issues.apache.org/jira/browse/IMPALA-7232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16530813#comment-16530813
]
Michael Ho edited comment on IMPALA-7232 at 7/3/18 4:36 AM:
------------------------------------------------------------
Yes, fixing IMPALA-6741 will definitely help. A missing profile update for a
particular instance just results really old timestamp in the profile. We also
need a marker in the profile to indicate whether the profile is final in order
to tackle situation like IMPALA-5555.
was (Author: kwho):
Yes, fixing IMPALA-6741 will definitely help. A missing profile update for a
particular instance just results really old timestamp in the profile. We also
need a marker in the profile to indicate whether the profile is final in order
to tackle situation like IMPALA-555.
> Display whether fragment instances' profile is complete
> -------------------------------------------------------
>
> Key: IMPALA-7232
> URL: https://issues.apache.org/jira/browse/IMPALA-7232
> Project: IMPALA
> Issue Type: Task
> Components: Distributed Exec
> Affects Versions: Impala 3.1.0
> Reporter: Michael Ho
> Assignee: Michael Ho
> Priority: Major
>
> While working on IMPALA-7213, it's noticed that we can fail to serialize or
> deserialize a profile for random reasons. This shouldn't be fatal: the
> fragment instance status can still be presented to the coordinator to avoid
> hitting IMPALA-2990. A missing profile in ReportExecStatus() RPC may result
> in incomplete or stale profile being presented to Impala client. It would be
> helpful to mark whether the profile may be incomplete and/or final in the
> profile output.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
