flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Till Rohrmann (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (FLINK-7804) YarnResourceManager does not execute AMRMClientAsync callbacks in main thread
Date Sun, 18 Mar 2018 18:02:00 GMT

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

Till Rohrmann closed FLINK-7804.
--------------------------------
    Resolution: Fixed

Fixed via 
1.6.0: 9538675caca24c83201e47bd26e4e725b2695217
1.5.0: eb666d8128ca5f63d735d87235959719c141fe93

> 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: Blocker
>              Labels: flip-6
>             Fix For: 1.5.0
>
>
> 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)

Mime
View raw message