vsantwana opened a new pull request, #1238:
URL: https://github.com/apache/flink-kubernetes-operator/pull/1238
## What is the purpose of the change
This PR removes the state size when reporting the cluster info for jobs
without checkpointing, which includes every batch job. For such a job, the
JobManager answers the checkpoint statistics request with 404, and the operator
treats that as a failure of the whole cluster info. Right now it logs a WARN
with a full stack trace on every reconcile, and never updates
`status.clusterInfo` or `status.taskManager.replicas` for the job:
```
WARN Exception while fetching cluster info
java.util.concurrent.ExecutionException:
org.apache.flink.runtime.rest.util.RestClientException: [Checkpointing has not
been enabled.]
```
The PR detects these jobs by the error message, with the check that
`getLastCheckpoint` already uses, and logs at DEBUG instead. It also makes
`getLastCheckpoint` log the same case at DEBUG without the stack trace.
Finally, it adds the Flink client timeout to the checkpoint statistics request,
as the other cluster info requests already have, so a slow JobManager fails the
cluster info like any other error instead of blocking the reconcile.
## Verifying this change
Extended 1 existing unit test.
## 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 changes to the `CustomResourceDescriptors`:
no
- Core observer or reconciler logic that is regularly executed: yes (the
deployment observer fetches the cluster info on every reconcile while the
JobManager is ready)
## 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 Code (Claude Opus 5.5)
--
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]
