Re: Solution to Solr Master-Slave single point of failure.

2014-06-30 Thread Alessandro Benedetti
Some further observation, 2014-06-19 1:40 GMT+01:00 Arcadius Ahouansou : > > Hello Erick. > > On 17 June 2014 16:52, Erick Erickson wrote: > >> The sticky parts of that solution (off the top of my head) are >> >> > assuring that the two masters have all the updates. How do you >> guarantee that

Re: Solution to Solr Master-Slave single point of failure.

2014-06-30 Thread Arcadius Ahouansou
Thanks Shawn and Erick for the valuable information. Just wondering: Is there a way to use the rest API to set the masterUrl on the slave ( or change masterUrl without restarting)? Checked http://wiki.apache.org/solr/SolrReplication#HTTP_API without success. Thanks. Arcadius. On 19 June 201

Re: Solution to Solr Master-Slave single point of failure.

2014-06-30 Thread Arcadius Ahouansou
Hi Alessandro. We are considering many options... including SolrCloud. Thanks. Arcadius. On 17 June 2014 14:54, Alessandro Benedetti wrote: > Hello Arcadius, > why not simple moving to SolrCloud that already addresses fault tolerance > and high availability ? > Simply imagine a configuratio

Re: Solution to Solr Master-Slave single point of failure.

2014-06-18 Thread Shawn Heisey
> I thought about this situation and I must admit that it's a tricky one. > We should offer the option to configure the slaves to swit> > Yes, I do understand that SolrCloud is the future. > However, removing this singlePointOfFailure from the traditional > master-slave deployment model would not r

Re: Solution to Solr Master-Slave single point of failure.

2014-06-18 Thread Arcadius Ahouansou
Hello Erick. On 17 June 2014 16:52, Erick Erickson wrote: > The sticky parts of that solution (off the top of my head) are > > > assuring that the two masters have all the updates. How do you guarantee > that the updates succeed and the two masters do, indeed, contain the exact > same informatio

Re: Solution to Solr Master-Slave single point of failure.

2014-06-17 Thread Erick Erickson
The sticky parts of that solution (off the top of my head) are > assuring that the two masters have all the updates. How do you guarantee that > the updates succeed and the two masters do, indeed, contain the exact same > information? > There'd have to be logic to insure that when the switch wa

Re: Solution to Solr Master-Slave single point of failure.

2014-06-17 Thread Alessandro Benedetti
Hello Arcadius, why not simple moving to SolrCloud that already addresses fault tolerance and high availability ? Simply imagine a configuration of : 1 shard, factor of replciation 3. And you have even a better scenario than 2 masters and 1 slave. Cheers 2014-06-17 14:43 GMT+01:00 Arcadius Ahoua

Solution to Solr Master-Slave single point of failure.

2014-06-17 Thread Arcadius Ahouansou
Hello. SolrCloud has been out for a while now. However, there are still many installations running Solr4 in the traditional master-slave setup. Currently, the Solr Master is the single point of failure of most master-slave deployment. This could be easily addressed by having : a- 2 indep