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

Posted to issues@flink.apache.org by "vinoyang (JIRA)" <ji...@apache.org> on 2019/05/16 11:50:00 UTC

[jira] [Updated] (FLINK-12039) Remove ASSIGNED_SLOT_UPDATER in Execution.tryAssignResource

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

vinoyang updated FLINK-12039:
-----------------------------
    Priority: Minor  (was: Major)

> Remove ASSIGNED_SLOT_UPDATER in Execution.tryAssignResource
> -----------------------------------------------------------
>
>                 Key: FLINK-12039
>                 URL: https://issues.apache.org/jira/browse/FLINK-12039
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Runtime / Coordination
>            Reporter: Andrey Zagrebin
>            Assignee: vinoyang
>            Priority: Minor
>
> After making access to ExecutionGraph single-threaded in FLINK-11417, we can simplify execution slot assignment in Execution.tryAssignResource and get rid of ASSIGNED_SLOT_UPDATER as it happens now only in one JM main thread. Though, it seems that we have to keep `assignedResource` as volatile at the moment which could be further investigated.



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