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

Fix possibility of concurrent status reports

Agile BoardAttach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • Impala 2.10.0
    • None
    • Backend
    • None
    • ghx-label-9

    Description

      The coordinator may receive multiple backend status reports concurrently for a few reasons:

      • The backend believes that sending the report failed and retries when in fact the first report did reach the coordinator.
      • A report is sent by the reporting thread at the same time that one is sent by Finalize().
      • Multiple fragments from the same backend send reports at the same time.

      This has the possibility of causing races. One such race was fixed in IMPALA-5749, but we should deal with the underlying issue of concurrent reports in a more complete way, rather than just trying to fix individual races as they become apparent.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            twmarshall Thomas Tauber-Marshall

            Dates

              Created:
              Updated:

              Slack

                Issue deployment