[IMPALA-4660] KuduScanNode may not terminate scanners when parent nodes reach limit

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Cannot Reproduce
• Affects Version/s: Impala 2.8.0
• Component/s: Backend
• Labels: kudu
• Target Version: Impala 2.11.0
• Assignee: Sailesh Mukil
• Reporter: Matthew Jacobs
• Created: 14/Dec/16 18:58
• Updated: 16/Oct/17 22:43
• Resolved: 16/Oct/17 22:43

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/