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

Retried queries that blacklist nodes should ensure they don't run on the blacklisted node

Attach filesAttach ScreenshotVotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Critical
    • Resolution: Fixed
    • None
    • Impala 4.0.0
    • None
    • None
    • ghx-label-9

    Description

      When a query is retried due to a node blacklisting event, there is no guarantee that the retried query will not run on the blacklisted node. When a node is blacklisted, it is only placed on the blacklist for a certain period of time (the first time it is blacklisted I think it is only about 12 seconds). It is possible that retrying the query takes a while (perhaps the query has to wait in the admission control queue again). So it is possible that the retried query will end up running on the node that it blacklisted during its original attempt, which is probably unwise because that node caused the query to fail.

      Attachments

        Activity

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

          People

            wzhou Wenzhe Zhou
            stakiar Sahil Takiar
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment