You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Maximilian Michels (JIRA)" <ji...@apache.org> on 2016/01/29 10:25:39 UTC

[jira] [Assigned] (FLINK-3300) Concurrency Bug in Yarn JobManager

     [ https://issues.apache.org/jira/browse/FLINK-3300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maximilian Michels reassigned FLINK-3300:
-----------------------------------------

    Assignee: Maximilian Michels

> Concurrency Bug in Yarn JobManager
> ----------------------------------
>
>                 Key: FLINK-3300
>                 URL: https://issues.apache.org/jira/browse/FLINK-3300
>             Project: Flink
>          Issue Type: Bug
>          Components: JobManager
>    Affects Versions: 1.0.0
>            Reporter: Stephan Ewen
>            Assignee: Maximilian Michels
>            Priority: Blocker
>             Fix For: 1.0.0
>
>
> The change to use the async ResourceManager client introduced concurrency problems: The ResourceManager callback threads run and change data structures at the same time as the actor methods, voiding the actor concurrency model.
> One example that can happen is that the callback tries to start containers while the ContainerLaunchContext is still not set (because the actor method is still in the StartYarnSession method).
> Bug introducing commit: https://github.com/apache/flink/commit/4e52fe4304566e5239996b3d48290e0c1f0772e8
> Quick fix could be to revert the commit. Better solution would be to let the callback methods send actor messages to the YobManager, rather than directly acting.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)