kaijaytu opened a new pull request, #570: URL: https://github.com/apache/yunikorn-site/pull/570
### Description Improve the quota preemption user guide with missing details identified in YUNIKORN-3248: - Clarify that `quota.preemption.delay` uses Go `time.Duration` format (e.g. `15s`, `5m`, `1h30m`) - Add "Triggering preconditions" section listing all 6 conditions required for quota preemption - Add "Configuration change scenarios" table covering max decrease, delay change, consecutive decreases, quota increase back, and max removal - Add "Restart behavior" section explaining that the preemption timer is in-memory only and resets on restart **Note on pending pods (JIRA item #3):** The JIRA suggests documenting that quota preemption only triggers when pending pods exist. After reviewing the code (`tryAcquirePreemption()` in `queue.go`, `internalQuotaPreemption()` in `scheduler.go`, and `quota_preemptor.go`), there is no pending pods check in the quota preemption flow. It triggers solely based on `allocatedResource > maxResource`. This is documented as a note in the "Triggering preconditions" section. **Observation:** `pnpm build` reports 50 pre-existing broken anchors across versioned docs (mostly 1.0.01.3.0), unrelated to this change. Would it be worth filing a separate issue to clean those up? Generated by GitHub Copilot (Claude Opus 4.6) ### Type of change - [x] Documentation - [x] Improvement ### Jira issue Jira ID : https://issues.apache.org/jira/browse/YUNIKORN-3248 - [x] I have created a Jira issue for this pull request - [x] The Jira ID is part of the title of this pull request ### AI Tooling - [x] The PR includes the phrase "Generated by GitHub Copilot (Claude Opus 4.6)" - [x] My use of AI contributions follows the ASF legal policy. ### How Has This Been Tested? - [x] `check_license.sh` returned an "all OK" result - [x] `local_build.sh run` generated a usable website ### Screenshots or other details N/A -- 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]
