[jira] [Closed] (FLINK-15744) Some TaskManager Task exception are logged as info

["Aljoscha Krettek (Jira)" <ji...@apache.org>]

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

Aljoscha Krettek closed FLINK-15744.
------------------------------------
    Fix Version/s: 1.11.0
       Resolution: Fixed

master: b38a70201ac34bdced145e00fd9d517d9da46d17

> Some TaskManager Task exception are logged as info
> --------------------------------------------------
>
>                 Key: FLINK-15744
>                 URL: https://issues.apache.org/jira/browse/FLINK-15744
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / Configuration
>    Affects Versions: 1.9.1
>         Environment: 1.9.1 on a recent ubuntu release
>            Reporter: Jason Kania
>            Assignee: Jason Kania
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.11.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> After investigating to find the cause for a submitted job alternating between the deploying and running states, I tried setting the logging to info level and realized that some deployment exceptions were being logged as info when they really should be a warning or error level.
> In particular, the following line (at line 960) of the 1.9.1 branch of the Task class logs as info:
> LOG.info("{} ({}) switched from {} to {}.", taskNameWithSubtask, executionId, currentState, newState, cause);
> This log line always has a non null exception cause so it would make sense to log at warning or error level for this state transition so it is more easily found.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)