Shawn, Actually we were using the preference parameter but recently we faced an issue where 1 pull replica got down(due to gcp machine restart) and requests started going to the NRT replica. Machine hosting NRT replica is pretty weak.
That's why I was experimenting with with shards parameter with all the urls of pull replicas. So request has no option to go to any other shards. Also planning to use shards.tolrent so that in case one or more replica is down , we can get the response from remaining replicas. Based on the Documentation link I have posted, it says that we can use but i cam not able to make it work. On Mon, 10 Oct, 2022, 6:14 pm Shawn Heisey, <apa...@elyograg.org> wrote: > On 10/10/22 06:00, Satya Nand wrote: > > Yes, we are using solr cloud. The reason I don't want to specify the > > shards' names is that a request can be sent to any replica of a shard > based > > on preference and availability but I specifically want to limit a request > > to a PULL-type replica of a shard. > > > > I am trying to replicate the behavior on this link, > > This is a perfect use case for the shards.preference parameter. Use > "shards.preference=replica.type:PULL" along with a list of shard names. > If there is at least one PULL replica available for a shard, it will be > used. It will only try other replica types as a last resort. > > > https://solr.apache.org/guide/8_4/distributed-requests.html#shards-preference-parameter > > Thanks, > Shawn > >
