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

Crash in scheduler when no backends are registered

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: Impala 2.7.0
    • Fix Version/s: Impala 2.8.0
    • Component/s: Backend
    • Labels:
      None

      Description

      The scheduler will crash when there are no backends registered and therefore the backend_config_ is empty. We should return an error instead, since without backend a query cannot be scheduled in a meaningful way. I will push a fix shortly.

        Activity

        Hide
        lv Lars Volker added a comment -

        IMPALA-4329: Prevent crash in scheduler when no backends are registered

        The scheduler crashed with a segmentation fault when there were no
        backends registered: After not being able to find a local backend (none
        are configured at all) in ComputeScanRangeAssignment(), the previous
        code would eventually try to return the top of
        assignment_ctx.assignment_heap in SelectRemoteBackendHost(), but that
        heap would be empty. Subsequently, when using the IP address of that
        heap node, a segmentation fault would occur.

        This change adds a check and aborts scheduling with an error. It also
        contains a test.

        Change-Id: I6d93158f34841ea66dc3682290266262c87ea7ff
        Reviewed-on: http://gerrit.cloudera.org:8080/4776
        Reviewed-by: Dan Hecht <dhecht@cloudera.com>
        Tested-by: Internal Jenkins

        Show
        lv Lars Volker added a comment - IMPALA-4329 : Prevent crash in scheduler when no backends are registered The scheduler crashed with a segmentation fault when there were no backends registered: After not being able to find a local backend (none are configured at all) in ComputeScanRangeAssignment(), the previous code would eventually try to return the top of assignment_ctx.assignment_heap in SelectRemoteBackendHost(), but that heap would be empty. Subsequently, when using the IP address of that heap node, a segmentation fault would occur. This change adds a check and aborts scheduling with an error. It also contains a test. Change-Id: I6d93158f34841ea66dc3682290266262c87ea7ff Reviewed-on: http://gerrit.cloudera.org:8080/4776 Reviewed-by: Dan Hecht <dhecht@cloudera.com> Tested-by: Internal Jenkins
        Hide
        lv Lars Volker added a comment -

        Change out for review here: https://gerrit.cloudera.org/#/c/4776/

        Show
        lv Lars Volker added a comment - Change out for review here: https://gerrit.cloudera.org/#/c/4776/

          People

          • Assignee:
            lv Lars Volker
            Reporter:
            lv Lars Volker
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development