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

[Bug] PerformanceConsumer does not stop at numMessages messages received #17747

Closed
2 tasks done
andrasbeni opened this issue Sep 20, 2022 · 0 comments · Fixed by #17750
Closed
2 tasks done

[Bug] PerformanceConsumer does not stop at numMessages messages received #17747

andrasbeni opened this issue Sep 20, 2022 · 0 comments · Fixed by #17750
Assignees
Labels
type/bug The PR fixed a bug or issue reported a bug

Comments

@andrasbeni
Copy link
Contributor

Search before asking

  • I searched in the issues and found nothing similar.

Version

master branch, 8b771a6

Minimal reproduce step

start ./pulsar-perf consume -u pulsar://localhost:6650 -m 100 topic
run ./pulsar-perf produce -u pulsar://localhost:6650 -m 110 topic in parallel

What did you expect to see?

pulsar-perf consume should have stopped after receiving 100 messages.

What did you see instead?

pulsar-perf consume did not stop even after 110 messages.

Anything else?

the field numMessages, that stores the value of the flag -m is never used.

Are you willing to submit a PR?

  • I'm willing to submit a PR!
@andrasbeni andrasbeni added the type/bug The PR fixed a bug or issue reported a bug label Sep 20, 2022
@andrasbeni andrasbeni changed the title [Bug] PerformanceConsumer does not stop at num-messages messages received [Bug] PerformanceConsumer does not stop at numMessages messages received Sep 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug The PR fixed a bug or issue reported a bug
Projects
None yet
1 participant