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

DMLs/DDLs can hang as a result of catalogd restart

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • Impala 4.2.0
    • None
    • Backend
    • None
    • ghx-label-5

    Description

      IMPALA-5476 added handling for changes in catalogd service ID during the lifetime of a DML/DDL query, but the loop that waits for a new catalogd service ID can wait indefinitely in case the DML/DDL was handled by the previous catalogd and restart happened just after replying to the coordinator:
      https://github.com/apache/impala/blob/d0fe4c604f72d41019832513ebf65cfe8f469953/be/src/service/impala-server.cc#L2204

      Could reproduce this by adding a sleep just before taking catalog_version_lock_ and restarting catalogd while a DML/DDL was waiting there. As a result the query hanged - it could be finished only by restarting catalogd. Canncelling the query also wouldn't help, the thread that handles the query is stuck until catalogd restart.

      Note that this issue may be present on all Impala versions that contain IMPALA-5476, but I haven't verified this and other changes could also affect the behavior (e.g. async DML support).

      Attachments

        Issue Links

        Activity

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

          People

            daniel.becker Daniel Becker
            csringhofer Csaba Ringhofer
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment