flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-8504) TaskExecutor does not properly deregisters JobManager from JobLeaderService
Date Tue, 30 Jan 2018 21:58:00 GMT

    [ https://issues.apache.org/jira/browse/FLINK-8504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16345880#comment-16345880
] 

ASF GitHub Bot commented on FLINK-8504:
---------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/flink/pull/5361


> 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
>            Assignee: Till Rohrmann
>            Priority: Critical
>              Labels: flip-6
>             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)

Mime
View raw message