You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Add option to mark a database as "sharded" so replication only connects to databases in the same shard, improving efficiency for sharded clusters.
10
+
- Reliability: ensure we never attempt to reference an audit entry when one is not recorded and always create an audit entry during conflict/CRDT resolutions; this prevents orphaned blobs and guarantees they can be cleaned up.
11
+
- Data integrity: assert that each transaction is recorded in the audit log.
12
+
- Maintenance: throttle blob cleanup to reduce system load and add a final log message indicating when orphan cleanup finishes.
13
+
- Fix: do not relocate records when their location is determined by id.
14
+
- Add a final cleanup log message when orphan blob cleanup finishes.
- Always record an audit entry when conflict/CRDT resolutions are performed so all blobs retain a reference for eventual cleanup
11
+
- Avoid referencing an audit entry when audit logging is disabled; ensure a new version is created when resolving a cache entry that replaces an existing one
12
+
- Blob cleanup improvements:
13
+
- Reduce cleanup rate to limit resource usage under load
14
+
- Add a final "orphan cleanup finished" log message
15
+
- Sharded deployments: do not connect to nodes with a database connection if the database is marked as sharded and is not in the same shard
16
+
- Stability: clear the application timeout timer to allow threads to exit gracefully when still running
0 commit comments