feat: migrate a running instance between nodes with an evolution gate#81
Merged
Conversation
Signed-off-by: Joshua Temple <joshua.temple@stablekernel.com>
joshua-temple
force-pushed
the
feat/cluster-migration
branch
from
8c5d98b to
e703f4a
Compare
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.
Adds live instance migration:
Capturesnapshots a running instance, its actor tree, and its machine definition into a wire-shippableCheckpoint, andRestorerebuilds it on another node — resuming in place (no entry actions re-run) and reconstructing the actors from the target's behavior palette (WithActorBehaviors). The move is gated on schema compatibility:Restorediffs the source machine IR (carried in the checkpoint) against the target machine viastate/evolutionand refuses withErrIncompatibleMigrationif the target is a breaking change, so an instance never resumes against a definition that would misread its persisted configuration; an additive or identical target is allowed. The checkpoint is all JSON, so it ships over any transport. This reuses the kernel's existing snapshot/restore and actor-snapshot seams — no kernel change. Coverage: cluster 92 percent. Additive; stdlib-only.