Hi Shawn,
Our Solr version is 7.7.0 and is deployed in the webapps directory of
Tomcat. Later, I tested the deployment with the bin/solr script, tested 7.7.0
and 7.7.3, and found that when maxshardspernode = 1, the same replica does not
appear on the same node.Maybe there's something wrong with the war package I
used before.
By the way, is there any difference between using backup data directory and
API backup in Solr of standalone mode? Are there any best practices in choosing
which backup method to use?
Many thanks,
Tony
From: Shawn Heisey
Date: 2022-01-17 11:28
To: users
Subject: Re: Consult the meaning of maxShardsPerNode
On 1/16/2022 7:22 PM, zhta...@163.com wrote:
> The following is my cluster status. The maxShardsPerNode configuration is 1,
> but I created a collection search1. Both replicas of shard1 are assigned to
> 192.168.52.164:8280_solr this node.
>
> Could this be a bug?
Hard to say. Yes, it could be a bug. You haven't indicated what
version of Solr you're on. SolrCloud has been around since version 4.0
and there have been a LOT of bugs fixed over the years. Some things I
am reading in bug reports seem to indicate that maxShardsPerNode may be
broken in current versions.
One thing you could do: Create the collection with one replica, then
utilize the ADDREPLICA action (and DELETEREPLICA if necessary) on the
collections API to move things around until they are placed in the
manner you want.
Thanks,
Shawn
