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

Posted to issues@flink.apache.org by "Gary Yao (JIRA)" <ji...@apache.org> on 2018/03/05 08:34:00 UTC

[jira] [Assigned] (FLINK-7804) YarnResourceManager does not execute AMRMClientAsync callbacks in main thread

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

Gary Yao reassigned FLINK-7804:
-------------------------------

    Assignee: Gary Yao

> YarnResourceManager does not execute AMRMClientAsync callbacks in main thread
> -----------------------------------------------------------------------------
>
>                 Key: FLINK-7804
>                 URL: https://issues.apache.org/jira/browse/FLINK-7804
>             Project: Flink
>          Issue Type: Bug
>          Components: Distributed Coordination, YARN
>    Affects Versions: 1.4.0, 1.5.0
>            Reporter: Till Rohrmann
>            Assignee: Gary Yao
>            Priority: Major
>              Labels: flip-6
>
> The {{YarnResourceManager}} registers callbacks at a {{AMRMClientAsync}} which it uses to react to Yarn container allocations. These callbacks (e.g. {{onContainersAllocated}} modify the internal state of the {{YarnResourceManager}}. This can lead to race conditions with the {{requestYarnContainer}} method.
> In order to solve this problem we have to execute the state changing operations in the main thread of the {{YarnResourceManager}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)