dohertj2/ScadaBridge
1
0
Fork 0
Code Issues 5 Pull Requests Actions Packages Projects Releases Wiki Activity

chore(deps): LocalDb 0.3.4 -> 0.3.7 (#130, scadaproj#53)

Browse Source 
Pins ZB.MOM.WW.LocalDb, .Replication and .Contracts at 0.3.7 (published
2026-11-12). Wire-compatible; no config or code change needed.

- 0.3.6 (scadaproj#36): the library sync service enforces
  LocalDb:Replication:ApiKey itself. LocalDbSyncAuthInterceptor is kept for
  its refuse-every-stream-when-blank rule; its doc comment is updated. The
  rig's site-a pair already carries one identical key on both nodes.
- 0.3.7 (scadaproj#16): a tombstone is held until the peer has it, so a
  node offline past TombstoneRetention no longer resurrects deleted rows.
  The survivor's ledger (sf_messages / site_events deletes) grows for the
  length of the outage; optional TombstoneHardCap bounds it.

Deploy notes added to the topology + installation guides, the S&F
requirement and CLAUDE.md: stop/start the pair together, same ApiKey on
both nodes, ledger growth while a peer is down.

Claude-Session: https://claude.ai/code/session_01GT67ACmpMR7b9LGRPLijMi
This commit is contained in:
Joseph Doherty
2026-11-12 13:44:53 -05:00
parent 25015442e5
commit 12fa7affc3
6 changed files with 43 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/deployment/installation-guide.md
+10 -2
View File
@@ -191,8 +191,16 @@ Ensure bidirectional TCP connectivity between all Akka.NET cluster peers. The re
**Stop both nodes of a site pair, upgrade both, then start both.** Rolling one node at a time is
not supported as of LocalDb Phase 2 — the legacy snapshot-compatibility handler that made a
mixed-version pair converge was deleted with the bespoke replicator, and a mixed pair now diverges
silently. See `docs/deployment/topology-guide.md` for the reasoning and for the related
`TombstoneRetention` bound on how long one node may stay offline.
silently. See `docs/deployment/topology-guide.md` for the reasoning.
For a replicated pair (LocalDb 0.3.7):
- `LocalDb:Replication:ApiKey` must be set, byte-identical, on **both** nodes (a `${secret:...}`
reference or an environment variable — never a literal in a shipped config). Both the library
and ScadaBridge's `LocalDbSyncAuthInterceptor` refuse the sync stream without it.
- While one node is down, the survivor's delete tombstones are held until the partner returns and
acks them, so its LocalDb file grows for the length of the outage. Deleted rows no longer
resurrect on rejoin, however long the outage (scadaproj#16).
## Post-Installation Verification