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

[fix][cli] Quit PerformanceConsumer after receiving numMessages messages #17750

Merged
merged 2 commits into from
Sep 27, 2022

Conversation

andrasbeni
Copy link
Contributor

@andrasbeni andrasbeni commented Sep 20, 2022

Fixes #17747

Motivation

PerformanceConsumer command line tool does not use its -m flag thus misleading its users.

Modifications

Check the total number of messages received against numMessages if the latter is non-zero.
Added integration test for pulsar-perf tool.

Verifying this change

  • Make sure that the change passes the CI checks.

This change can be verified as follows:

  • Added integration test.

Does this pull request potentially affect one of the following parts:

If the box was checked, please highlight the changes

  • Dependencies (add or upgrade a dependency)
  • The public API
  • The schema
  • The default values of configurations
  • The binary protocol
  • The REST endpoints
  • The admin CLI options
  • Anything that affects deployment

Documentation

  • doc-required
    (Your PR needs to update docs and you will update later)

  • doc-not-needed
    This is a bugfix

  • doc
    (Your PR contains doc changes)

  • doc-complete
    (Docs have been already added)

Matching PR in forked repository

PR in forked repository: andrasbeni#3

@andrasbeni andrasbeni changed the title [fix][cli] Quti PerformanceConsumer after receiving numMessages messages [fix][cli] Quit PerformanceConsumer after receiving numMessages messages Sep 20, 2022
@github-actions github-actions bot added the doc-not-needed Your PR changes do not impact docs label Sep 20, 2022
@andrasbeni
Copy link
Contributor Author

/pulsarbot rerun-failure-checks

1 similar comment
@andrasbeni
Copy link
Contributor Author

/pulsarbot rerun-failure-checks

@andrasbeni
Copy link
Contributor Author

Closing and reopening because pulsarbot did not rerun checks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug] PerformanceConsumer does not stop at numMessages messages received
4 participants