[DRILL-5854] IllegalStateException when empty batch is received.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.11.0
• Fix Version/s: 1.12.0
• Component/s: Execution - Flow
• Labels: ready-to-commit
• Assignee: Padma Penumarthy
• Reporter: Padma Penumarthy
• Reviewer: Paul Rogers
• Created: 07/Oct/17 01:42
• Updated: 11/Oct/17 17:59
• Resolved: 11/Oct/17 17:59

Description

When we get a batch with record count 0 and empty schema from one of the senders in the merge receiver,
the following exception is thrown sometimes.

Problem is that merge receiver is reading from the wrong sender when first batch is empty from one of the senders.
When first batch is empty, we are continuing without moving to the next sender.

Error: SYSTEM ERROR: IllegalStateException: Cleanup before finished. 0 out of 1 streams have finished

Fragment 0:0

[Error Id: 0dec4617-eb06-48fd-80c9-75e9c1e74ce2 on sidrill1:31010]

(java.lang.IllegalStateException) Cleanup before finished. 0 out of 1 streams have finished
org.apache.drill.exec.work.batch.BaseRawBatchBuffer.close():107
org.apache.drill.common.AutoCloseables.close():76
org.apache.drill.common.AutoCloseables.close():64
org.apache.drill.exec.work.batch.AbstractDataCollector.close():119
org.apache.drill.common.AutoCloseables.close():76
org.apache.drill.exec.work.batch.IncomingBuffers.close():140
org.apache.drill.exec.ops.FragmentContext.suppressingClose():436
org.apache.drill.exec.ops.FragmentContext.close():429
org.apache.drill.exec.work.fragment.FragmentExecutor.closeOutResources():320
org.apache.drill.exec.work.fragment.FragmentExecutor.cleanup():155
org.apache.drill.exec.work.fragment.FragmentExecutor.run():264
org.apache.drill.common.SelfCleaningRunnable.run():38
java.util.concurrent.ThreadPoolExecutor.runWorker():1149
java.util.concurrent.ThreadPoolExecutor$Worker.run():624
java.lang.Thread.run():748 (state=,code=0)

Issue Links

• links to: GitHub Pull Request #981