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

Posted to dev@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2018/01/24 14:48:00 UTC

[jira] [Created] (FLINK-8504) TaskExecutor does not properly deregisters JobManager from JobLeaderService

Till Rohrmann created FLINK-8504:
------------------------------------

             Summary: TaskExecutor does not properly deregisters JobManager from JobLeaderService
                 Key: FLINK-8504
                 URL: https://issues.apache.org/jira/browse/FLINK-8504
             Project: Flink
          Issue Type: Bug
          Components: Distributed Coordination
    Affects Versions: 1.5.0
            Reporter: Till Rohrmann
             Fix For: 1.5.0


The {{TaskExecutor}} should deregister jobs from the {{JobLeaderService}} once it no longer holds slots for this job. The problem is that before unregistering the job from the {{JobLeaderService}} in {{TaskExecutor#freeInternal}}, the actual slot is freed which also removes the {{JobID}} from the slot. Therefore, we lose the information to which job the slot belonged. An easy solution would be to return a {{SlotInformation}} object instead of the {{TaskSlot}} from {{TaskSlotTable#freeSlot}} which contains the respective information.



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