Hi Ivan,
It sounds to me like a bug in FlinkKinesisConsumer that it's not cancelling
properly. The change in the behaviour could have been introduced as a bug
fix [1], where we had to stop interrupting the source thread. This also
might be related or at least relevant for fixing [2].
Ivan, the st
In your case, the entry point is the `cleanUpInvoke` function called
by `StreamTask#invoke`.
@ro...@apache.org Could you take another look at this?
Best,
Yangze Guo
On Thu, Jul 29, 2021 at 2:29 AM Ivan Yang wrote:
>
> Hi Yangze,
>
> I deployed 1.13.1, same problem exists. It seems like that the
Hi Yangze,
I deployed 1.13.1, same problem exists. It seems like that the cancel logic has
changed since 1.11.0 (which was the one we have been running for almost 1
year). In 1.11.0, during the cancellation, we saw some subtask stays in the
cancelling state for sometime, but eventually the job
Hi, Ivan
My gut feeling is that it is related to FLINK-22535. Could @Yun Gao
take another look? If that is the case, you can upgrade to 1.13.1.
Best,
Yangze Guo
On Tue, Jul 27, 2021 at 9:41 AM Ivan Yang wrote:
>
> Dear Flink experts,
>
> We recently ran into an issue during a job cancellation a
Dear Flink experts,
We recently ran into an issue during a job cancellation after upgraded to 1.13.
After we issue a cancel (from Flink console or flink cancel {jobid}), a few
subtasks stuck in cancelling state. Once it gets to that situation, the
behavior is consistent. Those “cancelling tasks
