You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Michael Ho (JIRA)" <ji...@apache.org> on 2018/11/07 18:22:00 UTC

[jira] [Created] (IMPALA-7829) Send the final profile only after all fragment instances have been closed

Michael Ho created IMPALA-7829:
----------------------------------

             Summary: Send the final profile only after all fragment instances have been closed
                 Key: IMPALA-7829
                 URL: https://issues.apache.org/jira/browse/IMPALA-7829
             Project: IMPALA
          Issue Type: Bug
          Components: Distributed Exec
    Affects Versions: Impala 3.2.0
            Reporter: Michael Ho
            Assignee: Michael Ho


As shown in IMPALA-7828. there is some non-determinism on whether the errors detected in {{FragmentInstanceState::Close()}} will show up in the final profile sent to the coordinator. The reason is that the current code marks a fragment instance "done" after {{ExecInternal()}} completes but before {{Close()}} is called. There is a window in between when the final status report may be sent before {{Close()}} finishes. We should consider not sending the final report until {{Close()}} is done but we probably need to understand whether it has any implication to the overall reported query execution time. It should have no effect to the "First Rows Available" time for a query.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)