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

KuduScanNode may not terminate scanners when parent nodes reach limit

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Cannot Reproduce
    • Affects Version/s: Impala 2.8.0
    • Fix Version/s: None
    • Component/s: Backend
    • Labels:

      Description

      Related to IMPALA-4654 where the limit on a KuduScanNode was not respected and scanner threads would continue to completion.

      There may be an additional bug if a limit is on another node. We do not currently have a repro for this but believe there could be an issue because the KuduScanner doesn't check the scan node's done_ flag, or have some other way of being notified of cancellation except by checking the runtime state's status which may not be set in this case.

      This is based on a discussion in this CR, see for context:
      https://gerrit.cloudera.org/#/c/5493/

        Attachments

          Activity

            People

            • Assignee:
              sailesh Sailesh Mukil
              Reporter:
              mjacobs Matthew Jacobs
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: