Skip to content

Conversation

@dimitrovmaksim
Copy link
Member

@dimitrovmaksim dimitrovmaksim commented Jan 24, 2026

Resolves #6088

The Problem:

  • Two instances of the same subgraph/deployment exist (one active sgdXXX, one not sgdYYY).
  • Running graphman rewind sgdYYY ... to rewind the non-active deployment would incorrectly rewind the active deployment.
  • Cause: SubgraphStore::rewind and SubgraphStore::truncate accept DeploymentHash and resolved the hash to the active deployment.

What this PR does:

  • Changes SubgraphStore::rewind and SubgraphStore::truncate to accept and use DeploymentId.
  • Ensures the code fetches the correct Site and DeploymentStore for the exact deployment being targeted.
  • Keeps original safety checks and error messages.

Signed-off-by: Maksim Dimitrov <dimitrov.maksim@gmail.com>
@dimitrovmaksim dimitrovmaksim self-assigned this Jan 24, 2026
@dimitrovmaksim dimitrovmaksim changed the title fix(node, store): Use DeploymentId for rewind and truncate Fix rewinding the incorrect deployment instance Jan 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] Rewinding a specific sgd rewinds another instance of the same deployment, causing data corruption

1 participant