Saturday 07 July 2012 4:19:52 pm - 4 replies
Introduction
A common question I encounter in my consulting work is: how can Solr be configured for achieving scalability and high-availability?
There seems to be a lot of confusion around this topic, and the solutions I find deployed vary a lot. Often they are far from optimal, and offer little in both availability and scalability.
I will present here a simple configuration that needs little else than stock Apache and Solr servers to achieve both high-availability scalability. Read on for the details...
Tuesday 10 July 2012 2:51:05 pm
Feedback number 1: the next release of Solr will have a completely rewritten replication layer, which they name "cloud".
More details in the Solr site: http://lucene.apache.org/solr/solrnews.html
Tuesday 10 July 2012 2:52:34 pm
Feedback 2: the bug with replication of spellchecker index is described at https://issues.apache.org/jira/browse/SOLR-866
As a workaround, you can use a cronjob that uses wget/curl to force a spellcheck-index rebuild on the slave.
It should be run just after the "optimize index" cronjob has run on master (ie. wait for the time for the cronjob to finish on master + the delay for the main index files to be synced to the slave)
Modified on Tuesday 10 July 2012 2:52:55 pm by Gaetano Giunta
You must be logged in to post messages in this topic!