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/11/04 11:15:00 UTC
[jira] [Commented] (FLINK-12039) Remove ASSIGNED_SLOT_UPDATER in
Execution.tryAssignResource
[ https://issues.apache.org/jira/browse/FLINK-12039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16966567#comment-16966567 ]
vinoyang commented on FLINK-12039:
----------------------------------
[~gjy] Will open a PR for this issue,
> 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
(v8.3.4#803005)