[ 
https://issues.apache.org/jira/browse/FLINK-16728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Leonid Ilyevsky updated FLINK-16728:
------------------------------------
    Description: 
At some point I noticed that a few jobs got stuck (they basically stopped 
processing the messages, I could detect this watching the expected output), so 
I tried to cancel them.

The cancel operation failed, complaining that the job got stuck at 

StreamTaskActionExecutor$SynchronizedStreamTaskActionExecutor.run(StreamTaskActionExecutor.java:86)

and then the whole taskmanager shut down.

See the attached log.

This is actually happening practically every day in our staging environment 
where we are testing Flink 1.10.0.

  was:
At some point I noticed that a few jobs got stuck (they basically stopped 
processing the messages, I could detect this watching the expected output), so 
I tried to cancel them.

The cancel operation failed, complaining that the job got stuck at 

StreamTaskActionExecutor$SynchronizedStreamTaskActionExecutor.run(StreamTaskActionExecutor.java:86)

and then the whole taskmanager shut down.

See the attached log.


> Taskmanager dies after job got stuck and canceling fails
> --------------------------------------------------------
>
>                 Key: FLINK-16728
>                 URL: https://issues.apache.org/jira/browse/FLINK-16728
>             Project: Flink
>          Issue Type: Bug
>    Affects Versions: 1.10.0
>            Reporter: Leonid Ilyevsky
>            Priority: Major
>         Attachments: taskmanager.log.20200323.gz
>
>
> At some point I noticed that a few jobs got stuck (they basically stopped 
> processing the messages, I could detect this watching the expected output), 
> so I tried to cancel them.
> The cancel operation failed, complaining that the job got stuck at 
> StreamTaskActionExecutor$SynchronizedStreamTaskActionExecutor.run(StreamTaskActionExecutor.java:86)
> and then the whole taskmanager shut down.
> See the attached log.
> This is actually happening practically every day in our staging environment 
> where we are testing Flink 1.10.0.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to