Till Rohrmann created FLINK-25849:
-------------------------------------

             Summary: Differentiate TaskManager sessions
                 Key: FLINK-25849
                 URL: https://issues.apache.org/jira/browse/FLINK-25849
             Project: Flink
          Issue Type: Sub-task
          Components: Runtime / Coordination
    Affects Versions: 1.15.0
            Reporter: Till Rohrmann
            Assignee: Till Rohrmann


With the introduction of configurable {{ResourceID}} for {{TaskManager}} 
processes, it can happen that a restarted {{TaskManager}} process will be 
restarted with the same {{ResourceID}}. When it now tries to register at the 
{{JobMaster}}, the {{JobMaster}} won't recognize it as a new instance because 
it only compares the {{ResourceID}}. As a consequence, the {{JobMaster}} things 
that this is a duplicate registration and ignores it.

It would be better if the {{TaskManager}} would send a session id with the 
registration that could then be used to decide whether a new instance tries to 
register at the {{JobMaster}} and, therefore, the old one needs to be 
disconnected or whether the registration attempt is a duplicate.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to