We're switching to using composite routing in our solr cloud collection,
and of course that changes the document id. If I'm setting the document id
myself, what is the performance difference between q=id:123!4567 and
q=*:*&fq=some_field:4567?
Example:
Pre-indexed document:
- field1: 4567
-
I have the following setup:
- 6 shards on a collection called "jobs-09022020"
- 6 TLOG replicas (used only for indexing)
- 6 PULL replicas (used only for searching)
I want to scale the PULL replicas, 6 at a time, and have Solr add replicas
to that new node set when they come up and delete them whe
Hello! I'm new to the list and I have a bit of an issue that I could use
some help with.
I'm in the process of upgrading our Solr installation from legacy to cloud.
I'm new to the idea of Solr Cloud, so I've been wading through the
documentation and trying to get a basic cluster up and running. I'
that I can see.
--
Drew(i...@gmail.com)
http://wyntermute.dyndns.org/blog/
-- I Drive Way Too Fast To Worry About Cholesterol.
On Fri, Oct 18, 2019 at 3:11 AM Martijn Koster
wrote:
>
>
> > On 18 Oct 2019, at 00:25, Drew Kidder wrote:
>
> > * I'm using the following comm
ifferent.
>
> http://aadel.io
>
> On Fri, Oct 18, 2019 at 5:28 PM Drew Kidder wrote:
>
> > Thank you all for your suggestions! I appreciate the fast turnaround.
> >
> > My setup is using Amazon ECS for our solr cloud installation. Each ZK is
> in
> > its
n instead of holding it open. Am I interpreting
this correctly?
--
Drew(i...@gmail.com)
http://wyntermute.dyndns.org/blog/
-- I Drive Way Too Fast To Worry About Cholesterol.
On Fri, Oct 18, 2019 at 1:18 PM Drew Kidder wrote:
> Again, thank you all for the suggestions.
>
> My ZK ensemble is
