Release NativeLink v1.6.5 - #2696
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
2 participants
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.
What and why
Releases Nativelink v1.6.5. This commit is the version bump and changelog only; every change in it landed and was reviewed in its own PR.
Focuses on multi-replica scheduler correctness and large-blob handling. Two scheduler fixes stop replicas timing out each other's in-flight actions and stop orphaned actions leaking on the default configuration, and the remaining ByteStream paths now chunk oversized messages instead of failing them outright. Also adds full OTLP metric coverage for workers, gRPC, the scheduler, store tiers and health, and an optional TTL for Redis store keys. Anyone running more than one CAS replica, or proxying to another CAS, should upgrade.
How was this verified?
Each change was verified in its own PR: unit tests throughout. And the environment was tested in a live cluster with positive results.
Risk
Moderate, and concentrated in two behaviour changes rather than in the release mechanics.
max_action_executing_timeout_sat its default of 0, an action whose scheduler disappeared previously hung until the client gave up; it is now cleaned up after an hour.This change is