You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Robert Metzger (JIRA)" <ji...@apache.org> on 2019/02/13 10:26:00 UTC

[jira] [Commented] (FLINK-9776) Interrupt TaskThread only while in User/Operator code

    [ https://issues.apache.org/jira/browse/FLINK-9776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16767026#comment-16767026 ] 

Robert Metzger commented on FLINK-9776:
---------------------------------------

This change has actually been merged to Flink 1.6.0 (as you can see from the commit) [https://github.com/apache/flink/commit/53e6657658bc750b78c32e91fa7e2c02e8c54e33]

The fixversion has probably been pushed forward because the ticket was still open.

I'm adjusting the fix version from 1.6.4 to 1.6.0

> Interrupt TaskThread only while in User/Operator code
> -----------------------------------------------------
>
>                 Key: FLINK-9776
>                 URL: https://issues.apache.org/jira/browse/FLINK-9776
>             Project: Flink
>          Issue Type: Improvement
>          Components: Local Runtime
>            Reporter: Stephan Ewen
>            Assignee: Stephan Ewen
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.6.4, 1.8.0
>
>
> Upon cancellation, the task thread is periodically interrupted.
> This helps to pull the thread out of blocking operations in the user code.
> Once the thread leaves the user code, the repeated interrupts may interfere with the shutdown cleanup logic, causing confusing exceptions.
> We should stop sending the periodic interrupts once the thread leaves the user code.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)