When using Collections API CREATE action, I found that sometimes default
shard placement is correct (leader and replica on different servers) and
sometimes not. So I was looking for a simple and reliable way to ensure
better placement.
It seems like I will have to do it manually for best control, a
I've had a bad enough experience with the default shard placement that I
create a collection with one shard, add the shards where I want them, then
use add/delete replica to move the first one to the right machine/port.
Typically this is in a SolrCloud of dozens or hundreds of shards. Our
shards
Hi Isabelle,
If I understood correctly your question, you can check shard distribution
status at admin page
http://localhost:8983/solr/#/~cloud
if you started solr by using command like
$ java -Djetty.port=7574 -DzkHost=localhost:9983 -jar start.jar
(
https://cwiki.apache.org/confluence/disp
Thanks for the advice Erick.
Would you know what the underlying logic doing the shard distribution is?
Does it depend on the order in which each node joined the cluster or does
the collections api logic actually checks the node host IP to ensure even
distribution?
Best Regards,
Isabelle
On Wed
They should be pretty well distributed by default, but if you want to
take manual control, you can use the createNodeSet param on CREATE
(with replication factor of 1) and then ADDREPLICA with the node param
to put replicas for shards exactly where you want.
Best,
Erick
On Wed, Nov 5, 2014 at 2:1
Hello,
I am testing a small SolrCloud cluster on 2 servers. I started 2 nodes on
each server, so that each collection can have 2 shards with replication
factor of 2.
I am using below command from Collections API to create collection:
curl '
http://serveraddress/solr/admin/collections?action=CREA
