Suppose that for some reason you are not able to use SolrCloud and you are forced to use the old Master-Slave approach to guarantee High Availability.
In such a scenario, if the master failed, application are still able to search with slaves, but clearly, no more data can be indexed until the master is fully restored or configure some more complex topology (es http://stackoverflow.com/questions/6362484/apache-solr-failover-support-in-m aster-slave-setup ). In such a scenario could it be feasible to simply configure 2 or 3 identical instance of Solr and configure the application that transfer data to solr to all the instances simultaneously (the approach will be a DIH incremental for some core and an external application that push data continuously for other cores)? Which could be the drawback of using this approach? I've googled around, but did not find anything really useful. Thanks for any answer you could give me. -- Gian Maria Ricci Cell: +39 320 0136949 <http://mvp.microsoft.com/en-us/mvp/Gian%20Maria%20Ricci-4025635> <http://www.linkedin.com/in/gianmariaricci> <https://twitter.com/alkampfer> <http://feeds.feedburner.com/AlkampferEng>
