PoiBlackTea opened a new pull request, #568:
URL: https://github.com/apache/yunikorn-site/pull/568
### Description
[YUNIKORN-3216] Document unschedulable backoff settings and REST API updates
- Document queue configuration properties 'application.unschedasks.backoff'
and 'application.unschedasks.backoff.delay' in docs/user_guide/queue_config.md.
- Update REST API documentation in docs/api/scheduler.md:
* Include unschedasks backoff properties and fields ('unschedAskBackoff',
'askBackoffDelay') in Queue REST API json examples.
* Add 'backoffDeadline' field (UnixNano int64 per YUNIKORN-3326) to
Application REST API json response format.
### Type of change
Please delete options that are not relevant.
- [X] Documentation
- [ ] Improvement
- [ ] Feature
- [ ] Bug Fix
### Jira issue
Jira ID : https://issues.apache.org/jira/browse/YUNIKORN-3216
- [ ] 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
If an AI tool was used:
- [X] The PR includes the phrase "Generated by Antigravity IDE", where
Antigravity IDE is the name of the AI tool used.
- [X] My use of AI contributions follows the ASF legal policy.
Check https://www.apache.org/legal/generative-tooling.html for details.
### 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
Note for testing:
The backoffDeadline REST API field is documented using the int64 (UnixNano)
format per
[YUNIKORN-3326](https://issues.apache.org/jira/browse/YUNIKORN-3326). When
testing live, please use a yunikorn-core build that includes YUNIKORN-3326;
otherwise, older releases (e.g., 1.8.0) will output an RFC3339 string instead
of an int64 integer timestamp.
--
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]
