Paul Lorenz d8cedeb8ea Persist cluster id across migration snapshot restore. For #4104 ...

- adds a clusterId field to SyncSnapshotCommand and writes it into the database
  after the migration snapshot restore, so a controller bootstrapped by
  migrating a database ends up with a durable cluster id instead of an empty one
- the snapshot restore replaces the whole FSM database with the migration
  source, which carries no cluster id, so without this the id written during
  bootstrap was silently wiped and the node came up with an empty, non-durable
  cluster id, defeating the mesh cluster-id validation
- persists the raft index after the cluster id in RestoreSnapshot so the index
  remains the completion gate: a failure before it halts (SyncSnapshotCommand is
  a critical command) and replays/retries on restart rather than skipping the
  command with a blank cluster id
- fails RaftRestoreFromBoltDb when the cluster id is blank after bootstrap
- regenerates cmd.pb.go for the new field

2026-07-17 18:07:50 -04:00

..

command.go

Halt on critical-command apply failure instead of advancing. For #4104

2026-07-17 18:07:50 -04:00

generic_cmds.go

Persist cluster id across migration snapshot restore. For #4104

2026-07-17 18:07:50 -04:00

rate_limiter_test.go

Migrate to the sdk-golang v2 module path. For #3884

2026-06-23 15:43:39 -04:00

rate_limiter.go

Use success rate for adaptive rate limiter window sizing. Fixes #3636

2026-03-05 18:35:57 -05:00

registry.go

Optimize imports

2026-01-28 15:01:35 -05:00