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

kvs.ListKeysFiltered returns deleted keys #1802

Closed
kruegernet opened this issue Feb 14, 2025 · 2 comments
Closed

kvs.ListKeysFiltered returns deleted keys #1802

kruegernet opened this issue Feb 14, 2025 · 2 comments
Labels
defect Suspected defect such as a bug or regression

Comments

@kruegernet
Copy link
Contributor

Observed behavior

I create a kv bucket with RF=3 and storage=file
I create a couple of entries, delete them, minutes pass.
Using ListKeysFiltered function on the bucket from application code returns keys of the long (in computer time) deleted keys. This is unexpected.

Expected behavior

Users probably expect ListKeysFiltered will not return deleted keys. Alternatively ListKeysFiltered could take WatchOpt

Server and client version

server 2.10.25, client 1.39.0

Host environment

nats docker image on macos, on applie silicon

Steps to reproduce

Create single node or 3-node cluster
Create a kv bucket with RF=1 or RF=3 and storage=file
Create a couple of entries, delete them, wait a reasonable amount of time (seconds)
Use ListKeysFiltered with empty filter list, or wildcard or globbing filter list.
Receive the keys of recently deleted values from KV

@kruegernet kruegernet added the defect Suspected defect such as a bug or regression label Feb 14, 2025
@kruegernet
Copy link
Contributor Author

PR
#1802

@piotrpio
Copy link
Collaborator

Hello @kruegernet. Thank you for contribution, that was an oversight on our part! I reviewed the PR and have one additional ask.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
defect Suspected defect such as a bug or regression
Projects
None yet
Development

No branches or pull requests

2 participants