bq: We could create 2 separate collections.
- Requires re-indexing
- Code changes in our APIs and indexing process
- Lost ability to query all the docs at once ***
*** Not quite true. You can create an alias that points to multiple
collections. HOWEVER,
since the scores are computed using differen
Thanks for the information Erick –
I’ve learned there are 2 ‘classes’ of documents being stored in this collection.
There are about 4x as many documents in class A as class B.
When the documents are indexed, the document ID includes the key prefix like
‘A/1!’ or ‘B/1!’, which I understand spreads
having some replicas at 90G and some at 18G is totally unexpected with
compisiteID routing unless you're using "multi-level routing", see:
https://lucidworks.com/2014/01/06/multi-level-composite-id-routing-solrcloud/
But let's be clear what we're talking about here. I'm talking about
specifically
Thanks Erick/Chris for the information.
The page faults are occurring on each node of the cluster.
These are VMs running SOLR v7.2.1 on RHEL 7. CPUx8, 64GB mem.
We’re collecting GC information and using a DynaTrace agent, so I’m not sure if
/ how much that contributes to the overhead.
This clust
