You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@solr.apache.org by Satya Nand <sa...@indiamart.com.INVALID> on 2022/08/30 14:08:47 UTC
Forcing solr to run query on replica Nodes
Hi,
Currently, we have 8+1 solr nodes cluster. Where 1 Indexing node contains
all(8) NRT Primary shards. This is where all indexing happens. Then We have
another 8 nodes consisting of one pull replica of each primary shard.
For querying, we have used *shard.preference as PULL *so that all queries
are returned from pull replicas.
How can I force solr to use only pull replicas? in case one of the pull
replicas is not available then I want partial results to be returned from 7
replicas but never want to query on NRT replicas.
Re: Forcing solr to run query on replica Nodes
Posted by Satya Nand <sa...@indiamart.com.INVALID>.
.
On Thu, Sep 1, 2022 at 11:22 AM Satya Nand <sa...@indiamart.com> wrote:
> Thank you Shawn.
> If I eliminate this indexing node and create 8 NRT shards on these 8 query
> nodes. Meaning indexing will be happening on all 8 nodes and queries too.
>
> Will it create any impact on response time? currency commit interval is 15
> minus.
>
> On Tue, Aug 30, 2022 at 8:46 PM Shawn Heisey <ap...@elyograg.org.invalid>
> wrote:
>
>> On 8/30/22 08:08, Satya Nand wrote:
>> > For querying, we have used *shard.preference as PULL *so that all
>> queries
>> > are returned from pull replicas.
>> >
>> > How can I force solr to use only pull replicas? in case one of the pull
>> > replicas is not available then I want partial results to be returned
>> from 7
>> > replicas but never want to query on NRT replicas.
>>
>> With that shards.preference set to a replica type of PULL, it will only
>> go to NRT if it has no other choice.
>>
>> I am not aware of any way to *force* it to only use the preferred type.
>> Creating an option for that has the potential to interfere with high
>> availability, so I don't know how receptive devs will be to the idea.
>> You should open an enhancement issue in Jira.
>>
>> Thanks,
>> Shawn
>>
>>
Re: Forcing solr to run query on replica Nodes
Posted by Satya Nand <sa...@indiamart.com.INVALID>.
Thanks, Shawn.
I will try to create another post covering as many details as possible,
then somebody from this mailing list can help me in reviewing my
architecture,
On Wed, Sep 7, 2022 at 9:21 PM Shawn Heisey <ap...@elyograg.org.invalid>
wrote:
> On 8/31/22 23:52, Satya Nand wrote:
> > Thank you Shawn.
> > If I eliminate this indexing node and create 8 NRT shards on these 8
> query
> > nodes. Meaning indexing will be happening on all 8 nodes and queries too.
> >
> > Will it create any impact on response time? currency commit interval is
> 15
> > minus.
>
>
> Heavy indexing most likely would impact response time. Whether it's a
> significant impact is something I can't predict. There are simply too
> many unknowns, and even with a lot more information, any prediction
> would just be a guess.
>
> Thanks,
> Shawn
>
>
Re: Forcing solr to run query on replica Nodes
Posted by Shawn Heisey <ap...@elyograg.org.INVALID>.
On 8/31/22 23:52, Satya Nand wrote:
> Thank you Shawn.
> If I eliminate this indexing node and create 8 NRT shards on these 8 query
> nodes. Meaning indexing will be happening on all 8 nodes and queries too.
>
> Will it create any impact on response time? currency commit interval is 15
> minus.
Heavy indexing most likely would impact response time. Whether it's a
significant impact is something I can't predict. There are simply too
many unknowns, and even with a lot more information, any prediction
would just be a guess.
Thanks,
Shawn
Re: Forcing solr to run query on replica Nodes
Posted by Satya Nand <sa...@indiamart.com.INVALID>.
Thank you Shawn.
If I eliminate this indexing node and create 8 NRT shards on these 8 query
nodes. Meaning indexing will be happening on all 8 nodes and queries too.
Will it create any impact on response time? currency commit interval is 15
minus.
On Tue, Aug 30, 2022 at 8:46 PM Shawn Heisey <ap...@elyograg.org.invalid>
wrote:
> On 8/30/22 08:08, Satya Nand wrote:
> > For querying, we have used *shard.preference as PULL *so that all queries
> > are returned from pull replicas.
> >
> > How can I force solr to use only pull replicas? in case one of the pull
> > replicas is not available then I want partial results to be returned
> from 7
> > replicas but never want to query on NRT replicas.
>
> With that shards.preference set to a replica type of PULL, it will only
> go to NRT if it has no other choice.
>
> I am not aware of any way to *force* it to only use the preferred type.
> Creating an option for that has the potential to interfere with high
> availability, so I don't know how receptive devs will be to the idea.
> You should open an enhancement issue in Jira.
>
> Thanks,
> Shawn
>
>
Re: Forcing solr to run query on replica Nodes
Posted by Shawn Heisey <ap...@elyograg.org.INVALID>.
On 8/30/22 08:08, Satya Nand wrote:
> For querying, we have used *shard.preference as PULL *so that all queries
> are returned from pull replicas.
>
> How can I force solr to use only pull replicas? in case one of the pull
> replicas is not available then I want partial results to be returned from 7
> replicas but never want to query on NRT replicas.
With that shards.preference set to a replica type of PULL, it will only
go to NRT if it has no other choice.
I am not aware of any way to *force* it to only use the preferred type.
Creating an option for that has the potential to interfere with high
availability, so I don't know how receptive devs will be to the idea.
You should open an enhancement issue in Jira.
Thanks,
Shawn