Uploaded image for project: 'IMPALA'
  1. IMPALA
  2. IMPALA-9124 Transparently retry queries that fail due to cluster membership changes
  3. IMPALA-9748

Fix error reporting when AuxErrorInfoPB is present without an error

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Sub-task
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Backend
    • Labels:
      None
    • Epic Color:
      ghx-label-10

      Description

      As discussed in https://gerrit.cloudera.org/#/c/14824/24/be/src/runtime/query-driver.h@136, there is a bug in the error reporting path for query retries where it is possible for the error information set in TryQueryRetry is dropped. The impact is that the Status details (Status::AddDetail) set in TryQueryRetry won't get propagated to the client. This should only happen rarely, but it can only happen the ReportExecStatusRequestPB from a fragment contains a AuxErrorInfoPB entry, but no Status failure: https://gerrit.cloudera.org/#/c/14824/24/be/src/runtime/coordinator.cc@984

        Attachments

          Activity

            People

            • Assignee:
              wzhou Wenzhe Zhou
              Reporter:
              stakiar Sahil Takiar

              Dates

              • Created:
                Updated:

                Issue deployment