[
https://issues.apache.org/jira/browse/FLINK-21728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17301856#comment-17301856
]
Kezhu Wang commented on FLINK-21728:
------------------------------------
[~dwysakowicz] You are right. That is not possible.
Besides this, I once run into a weird call stack, I am not sure whether it is
deliberate or not. Following is the causal chain:
* {{SpillingThread}} fails.
* {{exceptionHandler}} is invoked, it will complete {{getIteratorFuture}}.
* Then it will call {{ExternalSorter.close}} synchronously due to
{{whenComplete}} in constructor of {{ExternalSorter}}.
* It will close {{SpillingThread}} which is current thread.
* {{ThreadBase.close}} will throw {{InterruptedException}} due to
{{interrupt}} and {{join}}.
* Exception swallowed. Execution continues.
I encountered this due to deliberate chaos from
{{UnsafeMemoryBudget.releaseMemory}}. It works. Just a bit weird.
> 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)
