Matthias Pohl

@zhengzhili333 sorry for the delay. But can you rebased the branch and remove any merge commits? That would help with the review

See [my comment](https://issues.apache.org/jira/browse/FLINK-34498?focusedCommentId=17821682&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17821682) in FLINK-34498. PR #24370 seems to fix the issue in a broader scale.

> Somewhat. There's no good reason to the log the entire config in the first place because it's already logged on start-up, so it also creates a bunch of noise....

Sorry for leaving you hanging for that long time. I was busy with other topics. Can you rebase the branch and bring the test case back? I hope I find...

Closing this one because [there are still issues](https://issues.apache.org/jira/browse/FLINK-34324?focusedCommentId=17814891&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17814891).

> Should we check if any on the other tests that are currently disabled for AdaptiveScheduler would now work, e.g. ? Yikes, that was actually my intention. But looks like...

I went a bit naively into this task. :-D Some of the tests are still failing with the `AdaptiveScheduler`. I analyzed the test failures and added a proper reasoning for...

@flinkbot run azure

I force-pushed a rebase to most-recent `master` w/o any other changes. I suspect that the [test failures](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=574080) we were seeing in CI are related to FLINK-34420

I fixed an indentation issue and rebased the branch. @MartijnVisser @JingGe can one of you go ahead and approve this one? So that we can finalize the efforts and merge...