Skip to content

fix(gms/sglang): preserve cache ownership through recovery - #15049

Draft
hutm wants to merge 1 commit into
hutm/gms-hardening-13-sglang-reservationsfrom
hutm/gms-hardening-14-sglang-recovery
Draft

hutm wants to merge 1 commit into
hutm/gms-hardening-13-sglang-reservationsfrom
hutm/gms-hardening-14-sglang-recovery

Conversation

@hutm

@hutm hutm commented Sep 18, 2026

Copy link
Copy Markdown
Contributor

Summary

Keep SGLang page ownership, CPU-retention state, and the native cache index coherent while persistent pages are adopted.

Why this is needed

Recovery must not expose a page to native eviction or reuse before its ownership and reconstructed index entry agree.

Validation

  • The cumulative publication tip is byte-identical to the locally validated implementation.
  • Cumulative focused validation: 994 passed, 1 skipped; the later vLLM-focused rerun passed 244 tests.
  • Local TP2 crash tests passed exact-output recovery for vLLM and SGLang; final performance qualification remains tracked in DEP: Production hardening for persistent GMS KV failover #15035.
  • This draft checkpoint still requires normal CI and reviewer validation before merge.

Stack

This PR is intentionally draft and stacked on its immediate predecessor.

Keep SGLang cache ownership and native index state coherent while a replacement adopts persistent pages.

Signed-off-by: mkhadkevich <mkhadkevich@nvidia.com>
@copy-pr-bot

copy-pr-bot Bot commented Sep 18, 2026

Copy link
Copy Markdown

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant