You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Biao Liu (JIRA)" <ji...@apache.org> on 2017/02/19 01:52:44 UTC
[jira] [Comment Edited] (FLINK-5836) Race condition between slot
offering and task deployment
[ https://issues.apache.org/jira/browse/FLINK-5836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15873399#comment-15873399 ]
Biao Liu edited comment on FLINK-5836 at 2/19/17 1:52 AM:
----------------------------------------------------------
+1
I think we have encountered this problem.
If nobody is working on this, I'll take it.
was (Author: sleepy):
+1
> Race condition between slot offering and task deployment
> --------------------------------------------------------
>
> Key: FLINK-5836
> URL: https://issues.apache.org/jira/browse/FLINK-5836
> Project: Flink
> Issue Type: Bug
> Components: Distributed Coordination
> Affects Versions: 1.3.0
> Reporter: Till Rohrmann
> Labels: flip-6
>
> The Flip-6 code has a race condition when offering slots to a {{JobManager}} which directly deploys tasks to the offered slots. In such a situation it is possible that the deploy call overtakes the acknowledge message for the slot offering. As a result, the slots are not marked yet as active and the deployment will fail.
> I propose to fix this problem by first activating all offered slots before sending the slot offer message to the {{JobManager}}. Consequently, we'll deactivate and free slots which haven't been accepted by the {{JobManager}} once we've received the offering acknowledge message.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)