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
Have you tried reproducing the issue with the latest release?
No
What is the hardware spec (RAM, CPU, OS)?
16Core CPU. 64GB Ram , Linux
What steps will reproduce the bug?
I am not completely sure about how to reproduce the bug. It will appear after I run several hours or days badger operation. After a restart, some of the expired keys is still there when I scan the related keys or get the key directly.
Can someone give me a bit of advice or guidance? Thanks.
What version of Badger are you using?
github.com/dgraph-io/badger/v4 v4.2.0
What version of Go are you using?
go 1.22.0
toolchain go1.22.4
Have you tried reproducing the issue with the latest release?
No
What is the hardware spec (RAM, CPU, OS)?
16Core CPU. 64GB Ram , Linux
What steps will reproduce the bug?
I am not completely sure about how to reproduce the bug. It will appear after I run several hours or days badger operation. After a restart, some of the expired keys is still there when I scan the related keys or get the key directly.
Can someone give me a bit of advice or guidance? Thanks.
Pseudocode:
Expected behavior and actual result.
Expired data should not be accessable via the basic get or scan APIs of badgerdb.
Should return
key not found
like errors.Additional information
shutdown is called when the program caught kill signal.
The
sync error
log didn't appear.The
Server exiting end ---
log appeared.shutdown code
badger options
The text was updated successfully, but these errors were encountered: