[
https://issues.apache.org/jira/browse/FLINK-21728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17302339#comment-17302339
]
Dawid Wysakowicz commented on FLINK-21728:
------------------------------------------
Isn't it the case that we may run into the issue all over the place in
{{DataSet}} and Blink {{Table/SQL API}} the two APIs that use
{{MemorySegments}}?
As you said we call the
1. {{memoryManager.releaseAll(invokable) in Task.doRun}}
2. We cancel the Task in a separate thread in a {{TaskCanceler}} which will
start closing operators which will start releasing its {{MemorySegments}}
Isn't it the case that basically the {{Task}} hijacks ownerships of
{{MemorySegments}} as a safety guard to close all remaining open segments? Or
am I missing something?
> DegreesWithExceptionITCase crash
> --------------------------------
>
> Key: FLINK-21728
> URL: https://issues.apache.org/jira/browse/FLINK-21728
> Project: Flink
> Issue Type: Sub-task
> Components: Library / Graph Processing (Gelly)
> Affects Versions: 1.13.0
> Reporter: Guowei Ma
> Priority: Blocker
> Labels: pull-request-available, test-stability
> Fix For: 1.13.0
>
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=14422&view=logs&j=ce8f3cc3-c1ea-5281-f5eb-df9ebd24947f&t=f266c805-9429-58ed-2f9e-482e7b82f58b
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
