Document maintenance scope for clients sharing a schema - #1371
Draft
yafi-s wants to merge 1 commit into
Draft
Conversation
Assisted-by: OpenAI Codex
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Clients configured for different queues still share schema-wide maintenance by default. This can surprise users with separate worker registries: the elected leader's rescuer discards a stuck job if its kind is unknown to that leader.
Add a short section beside client setup explaining maintenance scope, the need for shared job-kind registration, and separate schemas for independent applications. This documents current behavior and does not attempt the leadership-domain implementation in #1113.
Related to #1105.
Validation: checked the wording against JobRescuer.getStuckJobs, makeRetryDecision, Config.Schema, and the migration schema option. git diff --check passed. Documentation only; no Go code or tests changed.
AI-assisted contribution, opened as a draft for contributor review.