Thanks Shawn for sharing all possibilities , we will try to evaluate all
these.
On Mon, 10 Oct, 2022, 6:45 pm Shawn Heisey, wrote:
> On 10/10/22 06:58, Satya Nand wrote:
> > Actually we were using the preference parameter but recently we faced an
> > issue where 1 pull replica got down(due to
On 10/10/22 06:58, Satya Nand wrote:
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
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
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
Hi Shawn,
>
> The standard request handler is usually the one named "/select". You may
> want to add a new handler for this purpose.
We are already using a custom request handler, Actually, there is no
/select handler in our solr config.
your message subject says you are in cloud mode. If tha
On 10/10/22 01:57, Satya Nand wrote:
*"Do not add the shards parameter to the standard request handler; doing so
may cause search queries may enter an infinite loop. Instead, define a new
request handler that uses the shards parameter, and pass distributed search
requests to that handler."*
so
