MartijnVisser opened a new pull request, #28379:
URL: https://github.com/apache/flink/pull/28379

   ## What is the purpose of the change
   
   `RescaleTimelineITCase.testRescaleTerminatedByResourceRequirementsUpdated` 
is flaky on slow CI. It asserts that the second `updateJobResourceRequirements` 
RPC terminates the in-progress rescale started by the first update with 
terminal reason `RESOURCE_REQUIREMENTS_UPDATED`. That setter is a no-op once 
the rescale is already terminated. With the short cooldown (100 ms) and 
resource-stabilization (50 ms) timeouts shared by the parameterized 
configuration, the `DefaultStateTransitionManager` re-enters Idling and 
terminates the rescale with `NO_RESOURCES_OR_PARALLELISMS_CHANGE` before the 
second update is processed on a slow machine, producing the flaky assertion 
failure. This is a test-side timing assumption, not a product bug.
   
   ## Brief change log
   
     - For this case only, rebuild the fixture cluster in place with widened 
cooldown/stabilization (60 s) so the in-progress rescale stays alive across the 
single synchronous RPC round trip between the two updates.
     - The shared parameterized configuration used by the other cases is left 
untouched; the disabled-history parameter is skipped up front so it does not 
pay for a cluster rebuild it never asserts on.
   
   ## Verifying this change
   
   Existing assertions are unchanged. Verified by running 
`testRescaleTerminatedByResourceRequirementsUpdated` repeatedly in a loop 
locally without failure.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): no
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: no
     - The serializers: no
     - The runtime per-record code paths (performance sensitive): no
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
     - The S3 file system connector: no
   
   ## Documentation
   
     - Does this pull request introduce a new feature? no
     - If yes, how is the feature documented? not applicable
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes (Claude Opus 4.8 (1M context))
   
   Generated-by: Claude Opus 4.8 (1M context)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to