[jira] [Commented] (FLINK-20591) Remove JobManagerOptions.SCHEDULING_STRATEGY
[ https://issues.apache.org/jira/browse/FLINK-20591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17249082#comment-17249082 ] Till Rohrmann commented on FLINK-20591: --- Yes, I would suggest doing it as you proposed it. > Remove JobManagerOptions.SCHEDULING_STRATEGY > > > Key: FLINK-20591 > URL: https://issues.apache.org/jira/browse/FLINK-20591 > Project: Flink > Issue Type: Sub-task > Components: Runtime / Coordination >Affects Versions: 1.13.0 >Reporter: Till Rohrmann >Assignee: Robert Metzger >Priority: Major > Fix For: 1.13.0 > > > In order to disable the legacy scheduling strategies we need to remove the > {{JobManagerOptions.SCHEDULING_STRATEGY}}. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FLINK-20591) Remove JobManagerOptions.SCHEDULING_STRATEGY
[ https://issues.apache.org/jira/browse/FLINK-20591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17249048#comment-17249048 ] Robert Metzger commented on FLINK-20591: It seems that the approximate local recovery only works with the legacy scheduler. Shall I just disable the related test & file a ticket or is there another plan? > Remove JobManagerOptions.SCHEDULING_STRATEGY > > > Key: FLINK-20591 > URL: https://issues.apache.org/jira/browse/FLINK-20591 > Project: Flink > Issue Type: Sub-task > Components: Runtime / Coordination >Affects Versions: 1.13.0 >Reporter: Till Rohrmann >Assignee: Robert Metzger >Priority: Major > Fix For: 1.13.0 > > > In order to disable the legacy scheduling strategies we need to remove the > {{JobManagerOptions.SCHEDULING_STRATEGY}}. -- This message was sent by Atlassian Jira (v8.3.4#803005)