flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maximilian Michels (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (FLINK-3981) Don't log duplicate TaskManager registrations as exceptions
Date Mon, 30 May 2016 10:31:13 GMT

     [ https://issues.apache.org/jira/browse/FLINK-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Maximilian Michels closed FLINK-3981.
    Resolution: Fixed

Fixed with 93280069256a8afd3f3f5e263fcf2fa07ec14e0b

> 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
>              Labels: test-stability
>             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

This message was sent by Atlassian JIRA

View raw message