[FLINK-22698] RabbitMQ source does not stop unless message arrives in queue

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.13.1, 1.12.4
• Fix Version/s: 1.14.0, 1.12.5, 1.13.2
• Component/s: Connectors/ RabbitMQ
• Labels: pull-request-available
• Assignee: Michał Ciesielczyk
• Reporter: Austin Cawley-Edwards
• Created: 18/May/21 20:34
• Updated: 17/Nov/21 15:21
• Resolved: 22/Jun/21 11:35

Description

In a streaming job with multiple RMQSources, a stop-with-savepoint request has unexpected behavior. Regular checkpoints and savepoints complete successfully, it is only the stop-with-savepoint request where this behavior is seen.
 
Expected Behavior:
The stop-with-savepoint request stops the job with a FINISHED state.
 
Actual Behavior:
The stop-with-savepoint request either times out or hangs indefinitely unless a message arrives in all the queues that the job consumes from after the stop-with-savepoint request is made.
 
Current workaround:
Send a sentinel value to each of the queues consumed by the job that the deserialization schema checks in its isEndOfStream method. This is cumbersome and makes it difficult to do stateful upgrades, as coordination with another system is now necessary.
 
 
The TaskManager thread dump is attached.
 

Issue Links

• is related to: FLINK-23322 RMQSourceITCase.testStopWithSavepoint fails on azure due to timeout
• links to: GitHub Pull Request #16023
• links to: GitHub Pull Request #16222