spuru9 opened a new pull request, #29958:
URL: https://github.com/apache/flink/pull/29958
## What is the purpose of the change
The "Job failed during initialization of JobManager" alert can't appear
anymore. `/jobs/<id>` serves such a job as FAILED with an empty plan (HTTP
200), so `loadJob` never errors, and the alert read `root-exception`, which
FLINK-32688 removed. Meanwhile, the overview of such a job says "Job is not
running yet.".
## Brief change log
- Remove the unreachable alert, its error branch and its spec from
`JobDetailComponent`.
- On the job overview, show "Job failed" with a link to the Exceptions tab
instead of "Job is not running yet." when a FAILED job has no tasks. It doesn't
say "during initialization", because a FAILED job recovered after a JobManager
failover also has no tasks.
## Verifying this change
This change added tests and can be verified as follows:
- Added `JobOverviewComponent` specs for the failure message and the
FAILED flag. `ng test` (343 tests), lint and the production build pass.
- Manually verified on a local cluster with a job restored from a missing
savepoint: the overview shows the failure message, its link opens the
Exceptions tab with the cause, and a running job's overview is unchanged.
## 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 (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]