[
https://issues.apache.org/jira/browse/FLINK-9634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16523680#comment-16523680
]
ASF GitHub Bot commented on FLINK-9634:
---------------------------------------
Github user sihuazhou commented on a diff in the pull request:
https://github.com/apache/flink/pull/6208#discussion_r198129785
--- Diff: flink-tests/src/test/resources/log4j-test.properties ---
@@ -18,7 +18,7 @@
# Set root logger level to OFF to not flood build logs
# set manually to INFO for debugging purposes
-log4j.rootLogger=OFF, testlogger
+log4j.rootLogger=INFO, testlogger
--- End diff --
This looks like should be reverted.
> Deactivate previous location based scheduling if local recovery is disabled
> ---------------------------------------------------------------------------
>
> Key: FLINK-9634
> URL: https://issues.apache.org/jira/browse/FLINK-9634
> Project: Flink
> Issue Type: Bug
> Components: Distributed Coordination
> Affects Versions: 1.5.0
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.6.0, 1.5.1
>
>
> With Flink 1.5.0 we introduced local recovery. In order to make local
> recovery work we had to change the scheduling to be aware of the previous
> location of the {{Execution}}. This scheduling strategy is also active if
> local recovery is deactivated. I suggest to also disable the scheduling
> strategy if local recovery is not enabled.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
