We create “search feeds”, which are S3 files with one JSON object per line.
Documents going to Solr go into a feed file first. Periodically, the files are
fetched and loaded into Solr.
S3 is cross-region, so we could easily use this for multiple hot search
clusters. More often, we’ve used it fo
Thanks Anshum, Dima! Yes, I figure this approach will be quite challenging
to implement, and may not be worth the cost.
Anshum,
I had not thought of versioning (
https://solr.apache.org/guide/8_2/updating-parts-of-documents.html#document-centric-versioning-constraints),
but will consider it. Ye
Hi Matt,
I'll start by saying that this has been long due at my end.
There are a multitude of challenges with a hot-hot architecture involving
multiple SolrCloud clusters. An important question here is if you are going
to manage the versioning yourself. Also, if your updates would ever
overwrite
On 2022-03-01 5:02 PM, mtn search wrote:
I am curious if others have tried this and are willing to share any tips,
lessons learned, or things we should consider.
Not specific to Solr, but it's infinitely easier to do active-passive HA
than active-active (if that's what you mean buy hot-hot).
Hello,
My team is looking to deploy Solr 8 SolrCloud on two on-prem datacenters
via EKS. We are considering a HOT | HOT HA architecture between the data
centers where data would be indexed (duplicated) to SolrCloud instances in
both datacenters. Then via service (to be worked out) queries could g
