feat: cluster mode support for stress testing #1320
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cluster support implemented using Redis.
All available stress testing nodes registers under stress:nodes hset.
Starting stress test:
Example response:
Once we start the stress test, the master node will read "concurrent_requests" and divide it to the count of available nodes.
For example:
Node count: 4
concurrent_requests : 200
Each node will execute 200 / 4 = 50 concurrent requests.
Is used to receive results.
Where f6cbc007-e7a3-48ed-b325-a9c5697b5b0e is the stress test id, which we can find in response of /run API.
Example response:
Most important fields here :
is_finished - true (stress test finished), false (stress test is still running)
combined_metrics - is a map of combined performance metrics from all nodes for specific stress test