MartijnVisser opened a new pull request, #29214:
URL: https://github.com/apache/flink/pull/29214
## What is the purpose of the change
Backport of #28636 (`f9e0756fbfd`) to release-2.2.
The distribution rolls its log file during JobManager startup, so the
startup banner with the
program arguments frequently ends up in a rolled `.log.N` file that
`FlinkDistribution.searchAllLogs` skips. `DynamicParameterITCase` then waits
for that banner in
an unbounded loop, and the class has no `@Timeout`, so the whole Java e2e
leg runs until the CI
watchdog kills it at its time budget. On release-2.3 that took out E2E group
2 on the 2026-09-04,
09-11, 09-15 and 09-16 nightlies. The readiness loop, `FlinkDistribution`
and the distribution
log4j configuration are identical on this branch.
## Brief change log
- `FlinkDistribution.searchAllLogs` gains an `includeRolledLogs` overload,
so the banner is
found when it has been rolled. The existing two-argument method
delegates with `false`, so
the other callers are unchanged.
- `DynamicParameterITCase` waits with `CommonTestUtils.waitUtil(..., 1
minute, 500 ms, msg)`
instead of `while (!allProgramArgumentsLogged(dist)) Thread.sleep(500)`,
so a banner that
never arrives fails in a minute with a message rather than consuming the
leg's budget.
## Verifying this change
Clean cherry-pick: both changed files are byte-identical to the merged
master commit, and this
commit is byte-identical to the release-2.3 backport, both verified by blob
hash. The release-2.3
results carry over, so there is no separate run here. spotless green.
## 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
---
##### Was generative AI tooling used to co-author this PR?
- [X] Yes (Claude Opus 5, via Claude Code)
Generated-by: Claude Opus 5 (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]
