[SPARK-27111] A continuous query may fail with InterruptedException when kafka consumer temporally 0 partitions temporally

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.3.0, 2.3.1, 2.3.2, 2.3.3, 2.4.0, 2.4.1
• Fix Version/s: 2.3.4, 2.4.1, 3.0.0
• Component/s: Structured Streaming
• Assignee: Shixiong Zhu
• Reporter: Shixiong Zhu
• Created: 08/Mar/19 23:30
• Updated: 23/Mar/19 17:41
• Resolved: 09/Mar/19 23:22

Description

Before a Kafka consumer gets assigned with partitions, its offset will contain 0 partitions. However, runContinuous will still run and launch a Spark job having 0 partitions. In this case, there is a race that epoch may interrupt the query execution thread after `lastExecution.toRdd`, and either `epochEndpoint.askSync[Unit](StopContinuousExecutionWrites)` or the next `runContinuous` will get interrupted unintentionally.

Issue Links

• links to: GitHub Pull Request #24034