[
https://issues.apache.org/jira/browse/FLINK-40789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18132998#comment-18132998
]
Martijn Visser commented on FLINK-40789:
----------------------------------------
Two more on master, nightlies 2026-10-25 and 2026-10-26 (JDK 17), both the
cooldown race from my 2026-10-21 comment:
https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=80472&view=logs&j=0e7be18f-84f2-53f0-a32d-4a5e4a174679
(test_cron_adaptive_scheduler core,
RescaleTimelineHistoryEnabledITCase.testRescaleTerminatedByJobFailed)
https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=80488&view=logs&j=77a9d8e1-d610-59b3-fc2a-4766541e0e33
(test_cron_azure core,
testRecordNonTerminatedRescaleMergingWithNewRecoverableFailureTriggerCause)
{code}
[ERROR]
org.apache.flink.runtime.scheduler.adaptive.timeline.RescaleTimelineHistoryEnabledITCase.testRescaleTerminatedByJobFailed
-- Time elapsed: 11.08 s <<< ERROR!
java.util.concurrent.TimeoutException: Condition was not met within 10000 ms.
at
org.apache.flink.runtime.scheduler.adaptive.timeline.RescaleTimelineHistoryEnabledITCase.testRescaleTerminatedByJobFailed(RescaleTimelineHistoryEnabledITCase.java:134)
{code}
The UPDATE_REQUIREMENT rescale was terminated when the cooldown ended, before
the job failed:
{code}
00:59:45,104 ... Updated rescale is: Rescale{...
triggerCause=UPDATE_REQUIREMENT, terminalState=null, terminatedReason=null}
00:59:45,116 ... Transitioning from Cooldown to Idling, job
e5626e91abb30006a532d142b9a22625.
00:59:45,120 ... Current rescale Rescale{... triggerCause=UPDATE_REQUIREMENT,
terminalState=IGNORED, terminatedReason=NO_RESOURCES_OR_PARALLELISMS_CHANGE} is
null or terminated, so the update action is ignored.
00:59:45,121 ... Job Unnamed job (e5626e91abb30006a532d142b9a22625) switched
from state RUNNING to FAILING.
{code}
The second run has the same three rescales as buildId=80203 in my 2026-10-20
comment.
> RescaleTimelineITCase.testRecordRescaleForNewAvailableResource records three
> rescales instead of two
> ----------------------------------------------------------------------------------------------------
>
> Key: FLINK-40789
> URL: https://issues.apache.org/jira/browse/FLINK-40789
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
> Affects Versions: 2.3.1, 2.4.0
> Reporter: Martijn Visser
> Assignee: Naveen Joseph
> Priority: Critical
> Labels: test-stability
>
> https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=79368&view=logs&j=0da23115-68bb-5dcd-192c-bd4c8adebde1
> (master push 2026-09-23, test_ci core, JDK 17)
> {code}
> [ERROR]
> org.apache.flink.runtime.scheduler.adaptive.timeline.RescaleTimelineITCase.testRecordRescaleForNewAvailableResource
> -- Time elapsed: 0.722 s <<< FAILURE!
> java.lang.AssertionError:
> Expected size: 2 but was: 3 in:
> [Rescale{... rescaleAttemptId=3, ... preRescaleParallelism=4,
> postRescaleParallelism=6 ... triggerCause=NEW_RESOURCE_AVAILABLE,
> terminalState=COMPLETED ...},
> Rescale{... rescaleAttemptId=2, ... preRescaleParallelism=2,
> postRescaleParallelism=4 ... triggerCause=NEW_RESOURCE_AVAILABLE,
> terminalState=COMPLETED ...},
> Rescale{... rescaleAttemptId=1, ... preRescaleParallelism=null,
> postRescaleParallelism=2 ... triggerCause=INITIAL_SCHEDULE,
> terminalState=COMPLETED ...}]
> at
> org.apache.flink.runtime.scheduler.adaptive.timeline.RescaleTimelineITCase.lambda$testRecordRescaleForNewAvailableResource$2(RescaleTimelineITCase.java:170)
> at
> org.apache.flink.runtime.scheduler.adaptive.timeline.RescaleTimelineITCase.runAdaptedParameterizedAssertion(RescaleTimelineITCase.java:397)
> at
> org.apache.flink.runtime.scheduler.adaptive.timeline.RescaleTimelineITCase.testRecordRescaleForNewAvailableResource(RescaleTimelineITCase.java:164)
> {code}
>
>
> The test expects the initial schedule at parallelism 4 and
> one upscale to 6 after the third TaskManager starts. Here the job was first
> scheduled at 2 and went 2 -> 4 -> 6. The other RescaleTimelineITCase methods
> had similar races fixed in FLINK-40010, FLINK-40067 and FLINK-40076; this
> method has no ticket.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
