Thanks Shawn for sharing all possibilities , we will try to evaluate all these.
On Mon, 10 Oct, 2022, 6:45 pm Shawn Heisey, <apa...@elyograg.org> 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 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. > > Some choices: > > * Bump up the hardware hosting the NRT replicas so they can also handle > queries. > * Add another set of PULL replicas on separate hardware. > * Adjust your systems so that each one hosts a PULL replica for two > different shards. > * Rearrange things so that each system hosts an NRT replica for one > shard and a PULL replica for a different shard. > > Thanks, > Shawn > >
