(BLOOMBERG/ 919 3RD A) <
klian...@bloomberg.net> wrote:
> No worries, that's helpful. Thanks
>
> From: users@solr.apache.org At: 08/26/24 09:58:00 UTC-4:00To:
> users@solr.apache.org
> Subject: Re: TLOG/PULL query distribution
>
> Hey Kevin,
>
> I hope I'm no
No worries, that's helpful. Thanks
From: users@solr.apache.org At: 08/26/24 09:58:00 UTC-4:00To:
users@solr.apache.org
Subject: Re: TLOG/PULL query distribution
Hey Kevin,
I hope I'm not replying here too late.
The best docs on this are in the "SolrCloud Distributed Request
Hey Kevin,
I hope I'm not replying here too late.
The best docs on this are in the "SolrCloud Distributed Requests" page
[1]. In short though - by default Solr won't have any preference, it
does "just" a round-robin or random choice among the healthy replicas
for each shard. Users may provide a
Hello,
Given a mix of TLOG/PULL nodes in our solr cloud, the behavior I'm observing
from metrics is that CPU load is high for the leader TLOG (indexing) and the
PULL nodes (read queries) however for the most part the other TLOG nodes remain
very underutilized by comparison. My understanding is
