Uploaded image for project: 'IMPALA'
  1. IMPALA
  2. IMPALA-7829

Send the final profile only after all fragment instances have been closed

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: Impala 3.2.0
    • Fix Version/s: Impala 3.2.0
    • Component/s: Distributed Exec
    • Labels:
      None

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              kwho Michael Ho
              Reporter:
              kwho Michael Ho
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: