[ https://issues.apache.org/jira/browse/FLINK-22698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17351899#comment-17351899 ]
Austin Cawley-Edwards commented on FLINK-22698: ----------------------------------------------- [~nicholasjiang] – yes, I agree w/ Michał that this is something that should be considered w/ the FLIP-27 source, if it has not already been. [~cmick] Thanks for the research into other sources, the approach still sounds good to me as well as the user-facing configuration option. I'm not sure if there is precedent for it, but we could potentially introduce the fix in 1.14 with a reasonable timeout default (like the suggested 30s), and use the 0s default when backporting to 1.12 + 1.13 to maintain functionality. What do you think of that? Would it be more confusing to users? > RabbitMQ source does not stop unless message arrives in queue > ------------------------------------------------------------- > > Key: FLINK-22698 > URL: https://issues.apache.org/jira/browse/FLINK-22698 > Project: Flink > Issue Type: Bug > Components: Connectors/ RabbitMQ > Affects Versions: 1.12.0 > Reporter: Austin Cawley-Edwards > Assignee: Michał Ciesielczyk > Priority: Major > Attachments: taskmanager_thread_dump.json > > > 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. > -- This message was sent by Atlassian Jira (v8.3.4#803005)