liyude-tw opened a new pull request, #26809:
URL: https://github.com/apache/flink/pull/26809
## What is the purpose of the change
This pull request aligns Flink’s default for the YARN configuration option
`yarn.application-attempt-failures-validity-interval` with YARN itself.
The previous default (10 000 ms) caused unexpected endless AM restarts once
the interval between two failures exceeded ten seconds.
**Why `-1` instead of another fixed window?**
Since every environment performs differently, some restart AM in 30 seconds,
some in 3 seconds. There is no fixed time that fits everyone.
Setting the default to **`-1` (global counting)** removes the hidden
assumption and lets users choose a window that matches their own infrastructure
when needed.
JIRA: FLINK-38112
---
## Brief change log
* **`YarnConfigOptions`**
* `defaultValue` changed from `10000L` to `-1L`
* description text updated accordingly, including a correct REST-API link
* **Docs**
* Regenerated configuration HTML/Markdown via `generate-configdocs` so the
tables reflect the new default
---
## Verifying this change
This change is a **trivial configuration default update**.
No new tests are required; existing unit and IT cases already cover option
parsing, and the full Maven build (`mvn -T1C clean verify`) now passes on JDK
17.
---
## Does this pull request potentially affect one of the following parts
| Area | Impact |
|------|--------|
| Dependencies | **no** |
| Public API (`@Public`/`@PublicEvolving`) | **no** |
| Serializers | **no** |
| Runtime per-record code paths | **no** |
| Deployment / Recovery components (JM, Checkpointing, K8s/YARN, ZooKeeper)
| **yes – YARN only (default value change)** |
| S3 file-system connector | **no** |
---
## Documentation
*Does this pull request introduce a new feature?* **no**
The existing docs were **regenerated**; no manual doc text was added.
--
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]
