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
Trust database reload treated every update_database failure as fatal. Under concurrent reload and SIGHUP stress, LMDB can report MDB_MAP_FULL while committing the drop transaction, and the daemon exited even though the old trust database was still the published database.
The delete path now reports map exhaustion with the same code used by write failures, retries once after growing auto-sized maps, and returns a preserved-database status when the drop transaction never becomes visible. The reload path records the failure and keeps serving the previous trust database for that preserved state, while retaining the existing fatal behavior for rebuild failures after the database has been cleared.
0 commit comments