Have you considered putting them in the _same_ index? There's not much
penalty at all with having sparsely populated fields in a document, so
the fact that the two parts of your index had orthogonal fields
wouldn't cost you much and would solve the synchronization problem.
You can include a type f
Hello,
My team has been working with SOLR for the last 2 years. We have two main
indices:
1. documents
-index and store main text
-one record for each document
2. places (all of the geospatial places found in the documents above)
-index but don't store main text
-
You need dev, test, and live on separate boxes so that you can do capacity
tests. When you are sending queries to find out the max rate before overload,
you need to do that on dev or test, not live.
Also, you'll need to test new versions of Solr, so you need separate Solr
installations.
wunde
Background:
We have around 100 web sites of various sizes (in terms of indexable content)
and I'm trying to come up with the best architectural design from a performance
perspective.
- Each of the sites has a need for DEV, TEST and LIVE indices.
- The content on the sites divided into 5 group
