Implement in-process multi-dataset sync isolation across core, network, persistence, and tests
All checks were successful
NuGet Package Publish / nuget (push) Successful in 1m14s
All checks were successful
NuGet Package Publish / nuget (push) Successful in 1m14s
This commit is contained in:
@@ -30,6 +30,13 @@ To optimize reconnection, each node maintains a **Snapshot** of the last known s
|
||||
- If the chain hash matches, they only exchange the delta.
|
||||
- This avoids re-processing the entire operation history and ensures efficient gap recovery.
|
||||
|
||||
### Multi-Dataset Sync
|
||||
CBDDC supports per-dataset sync pipelines in one process.
|
||||
|
||||
- Dataset identity (`datasetId`) is propagated in protocol and persistence records.
|
||||
- Each dataset has independent oplog reads, confirmation state, and maintenance cadence.
|
||||
- Legacy peers without dataset fields interoperate on `primary`.
|
||||
|
||||
### Peer-Confirmed Oplog Pruning
|
||||
CBDDC maintenance pruning now uses a two-cutoff model:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user