[
https://issues.apache.org/jira/browse/FLINK-40789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18129629#comment-18129629
]
Martijn Visser commented on FLINK-40789:
----------------------------------------
One more on master, nightly 2026-10-21 (test_ci core, JDK 17):
https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=80342&view=logs&j=0da23115-68bb-5dcd-192c-bd4c8adebde1
{code}
[ERROR]
org.apache.flink.runtime.scheduler.adaptive.timeline.RescaleTimelineHistoryEnabledITCase.testRescaleTerminatedByJobCancelled
-- Time elapsed: 10.54 s <<< ERROR!
java.util.concurrent.TimeoutException: Condition was not met within 10000 ms.
at
org.apache.flink.runtime.scheduler.adaptive.timeline.RescaleTimelineHistoryEnabledITCase.testRescaleTerminatedByJobCancelled(RescaleTimelineHistoryEnabledITCase.java:105)
{code}
This is not the extra rescale from the description. The job started at
parallelism 4 and there are two rescales, but the UPDATE_REQUIREMENT one was
already terminated 1 ms after it was created, before the cancel, the same
cooldown race as testRecordInProgressRescale in my 2026-10-08 comment:
{code}
00:57:37,097 ... Updated rescale is: Rescale{...
triggerCause=UPDATE_REQUIREMENT, terminalState=null, terminatedReason=null}
00:57:37,099 ... Current rescale Rescale{... endTimestamp=1792544257098,
triggerCause=UPDATE_REQUIREMENT, terminalState=IGNORED,
terminatedReason=NO_RESOURCES_OR_PARALLELISMS_CHANGE} is null or terminated, so
the update action is ignored.
00:57:37,099 ... Job Unnamed job (bdcc843b054383dfeee79e062812d613) switched
from state RUNNING to CANCELLING.
{code}
The earlier master runs of this method (buildId=79750 and 80205) have the same
shape. Only the release-2.3 runs had three rescales.
> 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
(v8.20.10#820010)
