[
https://issues.apache.org/jira/browse/FLINK-5218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15714603#comment-15714603
]
ASF GitHub Bot commented on FLINK-5218:
---------------------------------------
Github user StefanRRichter commented on the issue:
https://github.com/apache/flink/pull/2920
I think the changed semantics makes actually more sense. It should also be
fine for all callers, as returning null to them was also previously possible
and IRC there should be no special meaning to an empty handle in 1.1.
> Eagerly close checkpoint streams on cancellation
> ------------------------------------------------
>
> Key: FLINK-5218
> URL: https://issues.apache.org/jira/browse/FLINK-5218
> Project: Flink
> Issue Type: Bug
> Components: State Backends, Checkpointing
> Affects Versions: 1.1.3
> Reporter: Stephan Ewen
> Assignee: Stephan Ewen
> Priority: Critical
> Fix For: 1.2.0, 1.1.4
>
>
> Some output streams perform blocking operations that cannot be properly
> interrupted. This causes cancellations to take very long when happening
> concurrently to large synchronous state snapshot operations.
> Closing the streams concurrently helps to abort these blocking operations.
> This might already be fixed in 1.2 by the {{CloseableRegistry}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
