Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Memory SyncArea: what it touches
Internal ChangesKind: in v2.1.275,
Internal ChangesSection of the release
What
The background process that keeps memory in sync now checks whether any of its data stores has become unusable. When that happens, it switches into a new 'off' retry state: it counts the number of retries, computes a randomized delay before trying again (to avoid retries all happening at once), and records the reason as off_retry instead of the usual periodic sync reason. The interval between resync attempts is now computed by a new helper function.
Why
This prevents memory sync from hammering a broken data store on a fixed schedule; instead it backs off with increasing, randomized delays until the store becomes usable again.
