Describe the bug
Passing in workload params to have more then 1 shard, and jsut getting 1.
To reproduce
After starting up a three node solr:
docker network create solrcloud-test
docker run --name solr-node1 -d \
--network solrcloud-test \
--publish 8983:8983 \
--memory 8g \
"apache/solr-nightly:10.0.0-SNAPSHOT-slim" solr start -f -m 2g --host solr-node1 -p 8983
docker run --name solr-node2 -d \
--network solrcloud-test \
--publish 8984:8984 \
--memory 8g \
"apache/solr-nightly:10.0.0-SNAPSHOT-slim" solr start -f -m 2g --host solr-node2 -z solr-node1:9983 -p 8984
docker run --name solr-node3 -d \
--network solrcloud-test \
--publish 8985:8985 \
--memory 8g \
"apache/solr-nightly:10.0.0-SNAPSHOT-slim" solr start -f -m 2g --host solr-node3 -z solr-node1:9983 -p 8985
I then start the workload via:
solr-orbit run --pipeline=benchmark-only --target-hosts=localhost:8983 --workload=nyc_taxis --workload-params="bulk_indexing_clients:4,num_shards:2" --kill-running-processes
I see the collection nyc_taxies get deleted and then created, but only with one shard:
Expected behavior
No response
Screenshots
If applicable, add screenshots to help explain your problem.
Host / Environment
No response
Additional context
No response
Relevant log output
Describe the bug
Passing in workload params to have more then 1 shard, and jsut getting 1.
To reproduce
After starting up a three node solr:
I then start the workload via:
I see the collection
nyc_taxiesget deleted and then created, but only with one shard:Expected behavior
No response
Screenshots
If applicable, add screenshots to help explain your problem.
Host / Environment
No response
Additional context
No response
Relevant log output