[
https://issues.apache.org/jira/browse/FLINK-22545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17382917#comment-17382917
]
Stephan Ewen commented on FLINK-22545:
--------------------------------------
The stack trace looks like the executor is creating a second thread after the
original thread terminated.
Looking at this more, the whole business of this thread factory that guards the
thread creation just looks like it doesn't really work.
I would vote to remove this altogether.
We either should just use a normal thread factory, or just manually create a
thread with a blocking queue of Runnables to pull from.
Before doing that, I would like to understand better why the executor thread
terminates - just to see if there is an issue in some other part of the system
that propagates a failure. Will push a hotfix to extend the logging.
> JVM crashes when runing
> OperatorEventSendingCheckpointITCase.testOperatorEventAckLost
> -------------------------------------------------------------------------------------
>
> Key: FLINK-22545
> URL: https://issues.apache.org/jira/browse/FLINK-22545
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination, Tests
> Affects Versions: 1.12.3
> Reporter: Guowei Ma
> Assignee: Stephan Ewen
> Priority: Critical
> Labels: pull-request-available, test-stability
> Fix For: 1.14.0, 1.12.5, 1.13.2
>
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=17501&view=logs&j=39d5b1d5-3b41-54dc-6458-1e2ddd1cdcf3&t=a99e99c7-21cd-5a1f-7274-585e62b72f56&l=4287
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
