[jira] [Created] (FLINK-20261) Uncaught exception in ExecutorNotifier due to split assignment broken by failed task

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Created] (FLINK-20261) Uncaught exception in ExecutorNotifier due to split assignment broken by failed task

Shang Yuanchun (Jira)
Andrey Zagrebin created FLINK-20261:
---------------------------------------

             Summary: Uncaught exception in ExecutorNotifier due to split assignment broken by failed task
                 Key: FLINK-20261
                 URL: https://issues.apache.org/jira/browse/FLINK-20261
             Project: Flink
          Issue Type: Bug
          Components: Connectors / FileSystem
    Affects Versions: 1.12.0
            Reporter: Andrey Zagrebin


While trying to extend FileSourceTextLinesITCase::testContinuousTextFileSource with recovery test after TM failure (TestingMiniCluster::terminateTaskExecutor, [branch|https://github.com/azagrebin/flink/tree/FLINK-20118-it]), I encountered the following case:
* SourceCoordinatorContext::assignSplits schedules async assignment (all reader tasks alive)
* call TestingMiniCluster::terminateTaskExecutor while doing writeFile in a loop of testContinuousTextFileSource
* causes graceful TaskExecutor::onStop shutdown
* causes TM/RM disconnect and failing slot allocations in JM by RM
* eventually causes SourceCoordinatorContext::unregisterSourceReader
* actual assignment starts (SourceCoordinatorContext::assignSplits: callInCoordinatorThread)
* registeredReaders.containsKey(subtaskId) check fails with IllegalArgumentException which is uncaught in single thread executor
* forces ThreadPool to recreate the single thread
* calls CoordinatorExecutorThreadFactory::newThread
* fails expected condition of single thread creation with IllegalStateException which is uncaught
* calls FatalExitExceptionHandler and exits JVM abruptly



--
This message was sent by Atlassian Jira
(v8.3.4#803005)