Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Queues that use in memory storage cannot run reclaim on abandonded localstorage queues #20

Closed
Dahaden opened this issue Aug 5, 2020 · 1 comment

Comments

@Dahaden
Copy link
Contributor

Dahaden commented Aug 5, 2020

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.

@Dahaden
Copy link
Contributor Author

Dahaden commented Aug 12, 2020

Fixed in PR 21 #21

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant