[FLINK-3981] Don't log duplicate TaskManager registrations as exceptions

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.1.0
• Fix Version/s: 1.1.0
• Component/s: Runtime / Coordination
• Labels: test-stability
• Assignee: Maximilian Michels
• Reporter: Maximilian Michels
• Created: 27/May/16 19:09
• Updated: 28/Feb/19 14:00
• Resolved: 30/May/16 10:30

Description

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.

Issue Links

• links to: GitHub Pull Request #2045