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
I noticed you merged my old PR so thought I'd bring this to your attention.
It looks like goleveldb may no longer be under active maintenance: syndtr/goleveldb#400. I found goleveldb infinite table "bloat" issues with my particular usage of siberite (very rapid key turnover - I doubt keys ever made it out of the memstore) that made me have to look for other queue solutions. Unfortunately, despite my best efforts I was never able to fully track down the cause of the bloat in goleveldb - my only suspicion was old keys were not being tombstoned correctly and removed during compaction cycles.
In the issue I linked above, a suggested alternative that appears to be under active development is https://github.com/lotusdblabs/lotusdb. I have no idea how much of a "drop in" replacement it would be but maybe worth considering if you are actively planning on continuing to work on siberite.
The text was updated successfully, but these errors were encountered:
Thanks for bringing this up. Have you tried to use siberite with the latest goleveldb version (instead of the vendored one)?
I'm not currently planning to actively work on siberite.
I did try and keep up with goleveldb releases to see if any resolved the issue but none of them did. However, it has probably been at least 2 years since I last tried and I've long since moved to a different team so not working on queue related things internally anymore.
@bogdanovich
I noticed you merged my old PR so thought I'd bring this to your attention.
It looks like goleveldb may no longer be under active maintenance: syndtr/goleveldb#400. I found goleveldb infinite table "bloat" issues with my particular usage of siberite (very rapid key turnover - I doubt keys ever made it out of the memstore) that made me have to look for other queue solutions. Unfortunately, despite my best efforts I was never able to fully track down the cause of the bloat in
goleveldb
- my only suspicion was old keys were not being tombstoned correctly and removed during compaction cycles.In the issue I linked above, a suggested alternative that appears to be under active development is https://github.com/lotusdblabs/lotusdb. I have no idea how much of a "drop in" replacement it would be but maybe worth considering if you are actively planning on continuing to work on siberite.
The text was updated successfully, but these errors were encountered: