-
Notifications
You must be signed in to change notification settings - Fork 468
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
[Bug] XINFO overflow when deleting pending message and consumer #2350
Comments
@LindaSummer Thanks for your detailed report. |
Hi @git-hulk , This should be forget to update the kvrocks/src/types/redis_stream.cc Lines 351 to 356 in d2e0feb
When remove consumer, the group will remove the pending count from the deleted consumer, the inconsistency emerged and may lead to overflow. kvrocks/src/types/redis_stream.cc Lines 687 to 688 in d2e0feb
kvrocks/src/types/redis_stream.cc Lines 717 to 720 in d2e0feb
|
Thank you for your report! If you know how to fix it, feel free to open a PR : ) |
Hi @PragmaTwice , I have opened a PR for this bugfix with related test case. Please take a look. Thanks very much. |
@LindaSummer Thanks for your nice catch and fix. |
Search before asking
Version
version: unstable
kvrocks_version: unstable
redis_version:4.0.0
git_sha1: d2e0feb
kvrocks_git_sha1: d2e0feb
redis_mode: standalone
kvrocks_mode: standalone
os: Linux 5.14.0-162.6.1.el9_1.0.1.x86_64 x86_64
gcc_version: 11.2.1
arch_bits: 64
process_id: 1
tcp_port: 6666
uptime_in_seconds: 1444
uptime_in_days: 0
Minimal reproduce step
Here is the step using redis-cli:
The redis-cli refuses to display the response value.
So, I use telnet to run the command and got response below.
What did you expect to see?
This is output from redis-cli.
This output from telnet.
What did you see instead?
redis-cli refuses to display the response.
kvrocks-server:6666> xinfo groups overflow-test Error: Bad integer value
telnet get the response from kvrocks-server.
Anything Else?
Hi kvrocks team,
I find the way to produce the bug during reading the PR of
XPENDING
#2190 .In conversations of the PR, it's suggested to use a separate PR to solve this problem.
I want to fix the bug and add related unit tests with it.
Best Regards,
Edward
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: