flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-7279) MiniCluster can deadlock at shut down
Date Fri, 28 Jul 2017 15:56:00 GMT

    [ https://issues.apache.org/jira/browse/FLINK-7279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16105146#comment-16105146

ASF GitHub Bot commented on FLINK-7279:

Github user NicoK commented on the issue:

    ok, I think, I understood the intention of `TaskExecutor#onFatalErrorAsync` wrong - it
is meant for outside `TaskExecutor` thread calls to run the error handler inside the `TaskExecutor`
    I'll create a new approach

> MiniCluster can deadlock at shut down
> -------------------------------------
>                 Key: FLINK-7279
>                 URL: https://issues.apache.org/jira/browse/FLINK-7279
>             Project: Flink
>          Issue Type: Bug
>          Components: Tests
>    Affects Versions: 1.4.0
>            Reporter: Till Rohrmann
>              Labels: flip-6
> The {{MiniCluster}} can deadlock in case if the fatal error handler is called while the
{{MiniCluster}} shuts down. The reason is that the shut down happens under a lock which is
required by the fatal error handler as well. If now the {{MiniCluster}} tries to shut down
the underlying RPC service which waits for all actors to terminate, it will never complete
because one actor is still waiting for the lock.
> One solution would be to ignore the fatal error handler calls if the {{MiniCluster}}
is shutting down.
> https://s3.amazonaws.com/archive.travis-ci.org/jobs/257811319/log.txt

This message was sent by Atlassian JIRA

View raw message