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
Something we have started to see recently in an extreme case, is when the localstorage is full of events from abandoned queues, localstorage-retry is unable to reclaim these queues.
In theory, queues should be able to be cleaned up as they move to localstorage, but in some extreme cases, we are seeing the clean up halt half way through and all new queues resort to in memory store.
Currently, this leaves localstorage-retry in an unrecoverable state, where is will always use in memory storage over local storage.
To fix this, we should be able to run the reclaim mechanism on localstorage, even when the main queue is in memory.
The text was updated successfully, but these errors were encountered:
Something we have started to see recently in an extreme case, is when the localstorage is full of events from abandoned queues, localstorage-retry is unable to reclaim these queues.
In theory, queues should be able to be cleaned up as they move to localstorage, but in some extreme cases, we are seeing the clean up halt half way through and all new queues resort to in memory store.
Currently, this leaves localstorage-retry in an unrecoverable state, where is will always use in memory storage over local storage.
To fix this, we should be able to run the reclaim mechanism on localstorage, even when the main queue is in memory.
The text was updated successfully, but these errors were encountered: