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

Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2018/03/27 12:46:00 UTC

[jira] [Created] (FLINK-9099) Failing allocated slots not noticed

Till Rohrmann created FLINK-9099:
------------------------------------

             Summary: Failing allocated slots not noticed
                 Key: FLINK-9099
                 URL: https://issues.apache.org/jira/browse/FLINK-9099
             Project: Flink
          Issue Type: Bug
          Components: Distributed Coordination
    Affects Versions: 1.5.0
            Reporter: Till Rohrmann
            Assignee: Till Rohrmann
             Fix For: 1.5.0


When allocating slots for eager scheduling, it can happen that allocated slots get failed after they are assigned to the {{Execution}} (e.g. due to a {{TaskExecutor}} heartbeat timeout). If there are still some uncompleted slot futures, then this will not be noticed since the {{Execution}} is assigned to the {{LogicalSlot}} only after all slot futures are completed. Therefore, the allocated slot failure will go unnoticed until this happens.

In order to speed up failures, we should directly assign the {{Execution}} to the {{LogicalSlot}} once the slot is assigned to the {{Execution}}.



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