[
https://issues.apache.org/jira/browse/IMPALA-7232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bikramjeet Vig resolved IMPALA-7232.
------------------------------------
Resolution: Fixed
Fix Version/s: Impala 3.2.0
The fragment instance states are already printed to the profile (IMPALA-6190 /
IMPALA-6246) which indicate the profile as being complete when the status
propagates to StateEvent::EXEC_END and prints "ExecInternal Finished" to the
profile
> 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
> Labels: ramp-up, supportability
> Fix For: Impala 3.2.0
>
>
> 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]
