[DRILL-2756] Check for cancellation in pseudo-blocking operations

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.8.0
• Fix Version/s: 0.9.0
• Component/s: Execution - Relational Operators
• Assignee: Jacques Nadeau
• Reporter: Chris Westin
• Created: 10/Apr/15 20:28
• Updated: 19/Apr/15 01:07
• Resolved: 19/Apr/15 01:07

Description

Certain operators, such as hash join, hash agg, and sort, consume all of their input before producing any output. For these, once they start working on their input, they don't check to see if the request has been cancelled. If another fragment fails (causing the overall query to be cancelled), or if the user requests a cancellation, these operators continue working because they never check.

We need to add checks (e.g., ask FragmentContext.isCancelled() or something like that) to these at periodic points. We don't want to check after every row, but it should be checked every so often (mimicing other operations, which generally get notified at batch boundaries).

Issue Links

• Is contained by: DRILL-2762 Fix situation where node failure hangs queries.
• is depended upon by: DRILL-2757 Verify operators correctly handle low memory conditions and cancellations