spuru9 opened a new pull request, #29682:
URL: https://github.com/apache/flink/pull/29682
## What is the purpose of the change
The Kerberized YARN application e2e test (custom fs plugin) fails
occasionally on the release-1.20 nightly: TaskManagers on a NodeManager with a
cold localization cache are still localizing when the test's 120 s slot request
timeout fires. Over the last 20 nightlies, the job normally finishes after
about 75 s, but slow runs take 116–118 s; two failed and one passed at 117 s.
## Brief change log
- Use Flink's default `slot.request.timeout` of 300 s instead of 120 s in
`common_yarn_docker.sh`.
- Let `wait_for_single_yarn_application` wait 300 + 120 s, so a job
without slots fails in Flink before the script gives up.
## Verifying this change
Ran `test_yarn_application_kerberos_docker.sh dummy-fs` locally with the
YARN workers throttled to 0.5 CPU (the cold node localized for about 110 s, as
in CI): it fails with the old script and passes with the new one.
## 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 (e2e test script
only)
- 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 (please specify the tool below)
Generated-by: Claude Opus 5.5 (Claude Code)
🤖 Generated with [Claude Code](https://claude.com/claude-code)
--
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]
