Repository navigation
Release v19.95.0
Several Chronicle kernels can now share one SQL database: schema provisioning is coordinated across processes and observer state lives in the database instead of in memory.
Changed
- SQL storage serializes schema provisioning across kernel processes with a database lock, so several kernels starting at once against one SQL Server or PostgreSQL database no longer race to create or upgrade the same tables (#5137)
- SQL storage persists observer in-flight events and handled counts in the database, so they survive a kernel restart and are shared between kernels using the same database (#5136)
- Groundwork for running the kernel as a multi-node cluster on SQL storage (part of #5127)