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

Posted to issues@flink.apache.org by "Maximilian Michels (JIRA)" <ji...@apache.org> on 2016/05/27 19:10:13 UTC

[jira] [Created] (FLINK-3981) Don't log duplicate TaskManager registrations as exceptions

Maximilian Michels created FLINK-3981:
-----------------------------------------

             Summary: Don't log duplicate TaskManager registrations as exceptions
                 Key: FLINK-3981
                 URL: https://issues.apache.org/jira/browse/FLINK-3981
             Project: Flink
          Issue Type: Bug
          Components: ResourceManager
    Affects Versions: 1.1.0
            Reporter: Maximilian Michels
            Assignee: Maximilian Michels
            Priority: Minor
             Fix For: 1.1.0


Duplicate TaskManager registrations shouldn't be logged with Exceptions in the ResourceManager. Duplicate registrations can happen if the TaskManager sends out registration messages too fast when the actual reply is not lost but still in transit.

The ResourceManager should simply acknowledge the duplicate registrations, leaving it up to the JobManager to decide how to treat the duplicate registrations (currently it will send an AlreadyRegistered to the TaskManager).

This change also affects our test stability because the Yarn tests check the logs for exceptions.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)