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

Test that queries are not retried if they cause an impalad to crash

    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-3

      Description

      IMPALA-9199 adds the core functionality for retrying queries, but it does not contain any tests that validate a query is not retried if the query itself caused an impalad to crash. If a query causes an impalad to crash, it should not be retried because it will likely just cause the impalad to crash again.

      There may not be a straightforward way to do this. I'm not sure how Impala can differentiate between query "x" causing a crash vs. anything else that can cause an impalad to crash. However, opening this JIRA to (1) document that this could be an issue, and (2) brainstorm any ideas.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              stakiar Sahil Takiar
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: