Route job starts to their target - #50
Merged
Merged
Conversation
A job start always landed on the proxy's default sled. An interactive start aimed at another sled would run there via gossip, but the client waited on the receiving sled and timed out after ten minutes, leaving an orphan. The start path now carries a target segment, like attach and output, and the proxy routes it. The client sends each start via the sled it resolved at signing time, so the wait watches the sled that runs the job. Co-Authored-By: Claude Mythos 5 <noreply@anthropic.com>
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.
A job start always landed on the proxy's default sled. An interactive start aimed at another sled would run there via gossip, but the client waited on the receiving sled and timed out after ten minutes, leaving an orphan. The start path now carries a
targetsegment, like attach and output, and the proxy routes it. The client sends each start via the sled it resolved at signing time, so the wait watches the sled that runs the job.