[FLINK-38112] Align default of yarn.application-attempt-failures-validity-interval with YARN

[liyude-tw]

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.

[flinkbot]

CI report:

• 5b1c9a1 Azure: FAILURE

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run azure re-run the last Azure build

[davidradl]

I am concerned about changing the default of an API, as this will result in change of behaviour for the user and could be seen as a regression. What was 10 seconds in now done globally.

[liyude-tw]

Below is the reasoning that led me to propose -1 and how I believe the change is safer and less surprising than the current default.

1. Few users intentionally depend on the current 10 s window
   The 10 s sliding window was introduced in PR [FLINK-12472][yarn] Support setting attemptFailuresValidityInterval o… #8400 by re-using the then-default Akka timeout. It wasn’t added to satisfy a concrete production need, so I think almost no one relies on it on purpose. We discover it after being surprised by extra restarts.

2. Hadoop YARN’s own default is -1 (global counting)
   Because Flink runs as a YARN ApplicationMaster, aligning with the upstream default reduces the cognitive overhead for operators who administer both systems.

3. The documentation and common intuition both imply “global counting”
   The description of yarn.application-attempts naturally suggests a total attempt limit. A hidden time window can therefore be surprising.

Risk-mitigation proposal

1. Upgrade guide
   Add the following note in the upgrade section for this release:

Starting with this release, yarn.application-attempt-failures-validity-interval defaults to -1 (global counting).
Clusters that benefit from the previous 10 s sliding window can retain the old behaviour by adding
yarn.application-attempt-failures-validity-interval: 10000

2. Release notes
   Repeat the same notice and example so that operators can quickly restore the former setting if needed.