[ https://issues.apache.org/jira/browse/FLINK-26400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500466#comment-17500466 ]
Zhu Zhu commented on FLINK-26400: --------------------------------- Here's what I see on the page "Limited integration with Flink’s Web UI: Adaptive Scheduler allows that a job’s parallelism can change over its lifetime. The web UI only shows the current parallelism the job." Seems the two problems listed above are not described in the known limitation. So I think they need to be fixed. But I agree that they are not blockers of 1.15 because the problem has been there for some versions and not blocker for users. Thanks for updating FLINK-22243. I have attached one picture to show problem #1. > Release Testing: Explicit shutdown signalling from TaskManager to JobManager > ---------------------------------------------------------------------------- > > Key: FLINK-26400 > URL: https://issues.apache.org/jira/browse/FLINK-26400 > Project: Flink > Issue Type: Improvement > Components: Runtime / Coordination > Affects Versions: 1.15.0 > Reporter: Niklas Semmler > Assignee: Zhu Zhu > Priority: Blocker > Labels: release-testing > Fix For: 1.15.0 > > Attachments: errors_on_opening_job_page_when_job_gets_no_resources.png > > > FLINK-25277 introduces explicit signalling between a TaskManager and the > JobManager when the TaskManager shuts down. This reduces the time it takes > for a reactive cluster to down-scale & restart. > > *Setup* > # Add the following line to your flink config to enable reactive mode: > {code} > taskmanager.host: localhost # a workaround > scheduler-mode: reactive > restart-strategy: fixeddelay > restart-strategy.fixed-delay.attempts: 100 > {code} > # Create a “usrlib” folder and place the TopSpeedWindowing jar into it > {code:bash} > $ mkdir usrlib > $ cp examples/streaming/TopSpeedWindowing.jar usrlib/ > {code} > # Start the job > {code:bash} > $ bin/standalone-job.sh start --main-class > org.apache.flink.streaming.examples.windowing.TopSpeedWindowing > {code} > # Start three task managers > {code:bash} > $ bin/taskmanager.sh start > $ bin/taskmanager.sh start > $ bin/taskmanager.sh start > {code} > # Wait for the job to stabilize. The log file should show that three tasks > start for every operator. > {code} > GlobalWindows -> Sink: Print to Std. Out (3/3) > (d10339d5755d07f3d9864ed1b2147af2) switched from INITIALIZING to > RUNNING.{code} > *Test* > Stop one taskmanager > {code:bash} > $ bin/taskmanager.sh stop > {code} > Success condition: You should see that the job cancels and re-runs after a > few seconds. In the logs you should find a line with the text “The > TaskExecutor is shutting down”. > *Teardown* > Stop all taskmanagers and the jobmanager: > {code:bash} > $ bin/standalone-job.sh stop > $ bin/taskmanager.sh stop-all > {code} -- This message was sent by Atlassian Jira (v8.20.1#820001)