docs(compression-coordinator): Add a user guide for using compression-coordinator. - #2456
docs(compression-coordinator): Add a user guide for using compression-coordinator.#2456LinZhihao-723 wants to merge 6 commits into
compression-coordinator.#2456Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
| Compared with `compression-scheduler`, `compression-coordinator` provides the following improvements | ||
| to the user experience, reliability, and performance: | ||
|
|
||
| * **Automatic failure recovery**: If a service fails or restarts, `compression-coordinator` | ||
| automatically resumes previously submitted jobs. Users do not need to restart them manually. | ||
| * **Improved resource utilization**: Compression jobs run in a Spider-managed execution environment, | ||
| allowing computational resources to be shared more effectively across all configured workers. | ||
| * **Configurable retries for compression failures**: `compression-coordinator` allows users to | ||
| configure a simple retry policy for failed compression tasks. Automatic retries can help recover | ||
| from transient issues, such as temporary network interruptions, without requiring user | ||
| intervention. | ||
| * TODO: Configure retry policy through <LINK> | ||
| * **Improved fairness across concurrent compression jobs**: `compression-coordinator` provides | ||
| two levels of concurrency control to improve fairness among compression jobs running concurrently: | ||
| * Coordinator-side rate limit: TODO, depends on #2435. | ||
| * Spider-side active job limit: Controls the maximum number of jobs that can make progress | ||
| concurrently while sharing compute resources in Spider. Jobs are admitted on a first-come, | ||
| first-served basis. | ||
| * **Data integrity**: Compression jobs coordinated by `compression-coordinator` publish their | ||
| results to the rest of the system through a dedicated commit stage. The commit operation is both | ||
| transactional and idempotent. | ||
| * A job-level failure does not result in partial updates. | ||
| * Internal retries do not result in duplicate updates |
There was a problem hiding this comment.
@junhaoliao Can you review this section to check if it makes sense (since it compares to the existing scheduling)?
Description
This PR depends on #2455.
Checklist
breaking change.
Validation performed