[Bug] PerformanceReader needs one more message than numMessages

[andrasbeni]

Search before asking

• I searched in the issues and found nothing similar.

Version

master; hash: 08df28a

Minimal reproduce step

Start bin/pulsar-perf read -u pulsar://localhost:6650 -n 100 topic.
Run bin/pulsar-perf produce -u pulsar://localhost:6650 -m 100 topic in parallel.

What did you expect to see?

pulsar-perf read quits and prints its statistics soon after the producer process finishes.

What did you see instead?

pulsar-perf read indefinitely waits for the next message

Anything else?

The ReaderListener increments the counter after checking the limit. Changing the order of the two solves the problem.

Are you willing to submit a PR?

• I'm willing to submit a PR!

[mattisonchao]

Cool and thanks!