How Operator Handle Flink Job Failure
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 581
- Forks
- 153
- PR merge metrics
- No merged PRs in 30d
Description
I want to check how the operator handle the flink job failure in 2 cases:
1. task manager failure:
Flink should handle this case by itself with checkpoint
2. job manager failure:
Is Operator able to automatically restart the Flink job when job manager failed with savepoint if enabled?
Does Operator support auto savepointing periodically?
Thanks,
Hui
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the operator's handling for TaskManager and JobManager failures, checkpoint recovery, and savepoint configuration; done means documenting whether each requested recovery and periodic autosave behavior is supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- distributed-systems, infrastructure
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100