-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Improve Simulation Tools and Add Documentation #328
Conversation
@@ -84,7 +84,7 @@ | |||
|
|||
@Parameter(names = { "-c", | |||
"--max-connections" }, description = "Max number of TCP connections to a single broker") | |||
public int maxConnections = 0; | |||
public int maxConnections = -1; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is already set that if you pass 0 it will disable the connection pool mechanism. Otherwise the client-lib default would be 1. So, I would say to set the default to 1 in this tool, so that it is more explicit what the resulting number of connection will be.
bin/pulsar-perf
Outdated
simulation-controller Run a simulation controller to give commands to servers | ||
produce Run a producer | ||
consume Run a consumer | ||
monitor Continuously receive broker data and/or load reports |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
monitor-load-manager
? Or can this be used in more general testing scenarios?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A think monitor-brokers
would be good, since it is really just printing out broker data in general.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
* Add documentation, improve simulation tools. * Add global summary for monitor * monitor -> monitor-brokers * Don't modify performance producer/consumer * Use property/cluster instead of cluster/property for simulation * Fix regex
simplify `MessageIdUtils.peekOffsetFromEntry` by use `Commands.peekBrokerEntryMetadataIfExist` directly
Motivation
The load simulation tools introduced in #303 did not yet have documentation and performed crudely in a few cases. This PR adds documentation and improves these tools.
Modifications
Result
The monitor may be started for either load manager using
pulsar-perf monitor
. Documentation for simulation tools is now present and those tools have been improved.