You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "XComp (via GitHub)" <gi...@apache.org> on 2026/09/04 15:49:37 UTC
[PR] [FLINK-40554][runtime] Skipping job recovery for jobs with broken execution plan instead of failing cluster recovery hidden behind newly introduced config parameter cluster.job-error-isolation.enabled [flink]
XComp opened a new pull request, #29107:
URL: https://github.com/apache/flink/pull/29107
The old implementation treated ExecutionPlan recovery errors as cluster-wide fatal causing the JobManager to fail over. This would cause other jobs on the same JobManager to failover as well. Enabling the new feature through the newly added configuration parameter makes the job recovery being skipped rather than failing the JobManager since the job wouldn't recover anyway. Cleanup needs to be handled manually by the operator. The error is revealed via error logs.
## What is the purpose of the change
Creates new configuration parameter (with the feature being disabled by default). Enabling the feature would skip job recovery for that job and emits an error log message instead for manual cleanup. This prevents JobManager failover.
## Brief change log
* Introduces new exception that's used when an error occurs during ExecutionPlan loading
* The new error is handled through an error log message instead of forwarding the error if the feature is enabled.
## Verifying this change
* Added separate unit tests to cover the behavior
## 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: yes
- The S3 file system connector: no
## Documentation
- Does this pull request introduce a new feature? no
- If yes, how is the feature documented? docs
---
##### Was generative AI tooling used to co-author this PR?
- [X] Yes (please specify the tool below)
Generated-by: Claude
--
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: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] [FLINK-40554][runtime] Skipping job recovery for jobs with broken execution plan instead of failing cluster recovery hidden behind newly introduced config parameter cluster.job-error-isolation.enabled [flink]
Posted by "XComp (via GitHub)" <gi...@apache.org>.
XComp commented on PR #29107:
URL: https://github.com/apache/flink/pull/29107#issuecomment-5568690098
Closing PR for the reason stated in the parent Jira issue [FLINK-40553](https://issues.apache.org/jira/browse/FLINK-40553?focusedCommentId=18112263&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-18112263):
> Reiterating over the problem space let me re-evaluate the issue: Corrupted or missing Flink-owned data points to some unknown cause that should be investigated and mitigated rather then narrowed down to job scope because it could have caused inconsistencies in other places. Keeping the cluster-wide failure makes sense in that case.
--
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: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] [FLINK-40554][runtime] Skipping job recovery for jobs with broken execution plan instead of failing cluster recovery hidden behind newly introduced config parameter cluster.job-error-isolation.enabled [flink]
Posted by "XComp (via GitHub)" <gi...@apache.org>.
XComp closed pull request #29107: [FLINK-40554][runtime] Skipping job recovery for jobs with broken execution plan instead of failing cluster recovery hidden behind newly introduced config parameter cluster.job-error-isolation.enabled
URL: https://github.com/apache/flink/pull/29107
--
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: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] [FLINK-40554][runtime] Skipping job recovery for jobs with broken execution plan instead of failing cluster recovery hidden behind newly introduced config parameter cluster.job-error-isolation.enabled [flink]
Posted by "flinkbot (via GitHub)" <gi...@apache.org>.
flinkbot commented on PR #29107:
URL: https://github.com/apache/flink/pull/29107#issuecomment-5543180314
<!--
Meta data
{
"version" : 1,
"metaDataEntries" : [ {
"hash" : "2371f5fd8a1f59fcf4f3b30da34f35fad5ad5d16",
"status" : "UNKNOWN",
"url" : "TBD",
"triggerID" : "2371f5fd8a1f59fcf4f3b30da34f35fad5ad5d16",
"triggerType" : "PUSH"
} ]
}-->
## CI report:
* 2371f5fd8a1f59fcf4f3b30da34f35fad5ad5d16 UNKNOWN
<details>
<summary>Bot commands</summary>
The @flinkbot bot supports the following commands:
- `@flinkbot run azure` re-run the last Azure build
</details>
--
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: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org