You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2019/12/03 21:50:00 UTC
[jira] [Updated] (FLINK-15045) SchedulerBase should only log the
RestartStrategy in legacy scheduling mode
[ https://issues.apache.org/jira/browse/FLINK-15045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated FLINK-15045:
-----------------------------------
Labels: pull-request-available (was: )
> SchedulerBase should only log the RestartStrategy in legacy scheduling mode
> ---------------------------------------------------------------------------
>
> Key: FLINK-15045
> URL: https://issues.apache.org/jira/browse/FLINK-15045
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination
> Affects Versions: 1.10.0
> Reporter: Gary Yao
> Assignee: Gary Yao
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.10.0
>
>
> In ng scheduling, we configure {{ThrowingRestartStrategy}} in the execution graph to assert that legacy code paths are not executed. Hence, the restart strategy should not be logged in ng scheduling mode. Currently, the following obsolete log message is logged:
> {noformat}
> 2019-12-03 20:22:14,426 INFO org.apache.flink.runtime.jobmaster.JobMaster - Using restart strategy org.apache.flink.runtime.executiongraph.restart.ThrowingRestartStrategy@44003e98 for General purpose test job (9af8d0845d449f3c3447f817b2150bc8).
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)