Re: solrcloud 4.3.1 - stability and failure scenario questions

2013-06-24 Thread Shalin Shekhar Mangar
Thanks for bringing that up Andre. I'll take a look at the patches. 2013/6/24 Andre Bois-Crettez : > On 06/23/2013 05:53 AM, Shalin Shekhar Mangar wrote: >> >> Use shards.tolerant=true to return documents that are available in the >> shards that are still alive. > > Beware that currently shards.to

Re: solrcloud 4.3.1 - stability and failure scenario questions

2013-06-24 Thread Andre Bois-Crettez
On 06/23/2013 05:53 AM, Shalin Shekhar Mangar wrote: Use shards.tolerant=true to return documents that are available in the shards that are still alive. Beware that currently shards.tolerant=true prevents grouping and facets : https://issues.apache.org/jira/browse/SOLR-3369 -- André Bois-Cret

Re: solrcloud 4.3.1 - stability and failure scenario questions

2013-06-24 Thread Shalin Shekhar Mangar
On Mon, Jun 24, 2013 at 12:16 AM, Utkarsh Sengar wrote: > Thanks! > > 1. "shards.tolerant=true" works, shouldn't this parameter be default? A whole shard being unavailable is a big deal. The default behavior should not hide such a condition. Some people may be willing to take a hit on coverage to

Re: solrcloud 4.3.1 - stability and failure scenario questions

2013-06-23 Thread Utkarsh Sengar
Thanks! 1. "shards.tolerant=true" works, shouldn't this parameter be default? 2. Regarding zk, yes it should be outside the solr nodes and I am evaluating what difference does it make. 3. Regarding usecase: Daily queries will be about 100k to 200k, not much. The total data to be indexed is about

Re: solrcloud 4.3.1 - stability and failure scenario questions

2013-06-22 Thread Shalin Shekhar Mangar
Use shards.tolerant=true to return documents that are available in the shards that are still alive. Typically people setup ZooKeeper outside of Solr so that solr nodes can be added/removed easily independent of ZooKeeper plus it isolates ZK from large GC pauses due to Solr's garbage. See http://wi

Re: solrcloud 4.3.1 - stability and failure scenario questions

2013-06-22 Thread Utkarsh Sengar
Thanks Anshum. Sure, creating a replica will make it failure resistant, but death of one shard should not make the whole cluster unusable. 1/3rd of the keys hosted in the killed shard should be unavailable but others should be available. Right? Also, any suggestions on the recommended size of

Re: solrcloud 4.3.1 - stability and failure scenario questions

2013-06-22 Thread Anshum Gupta
You need to have at least 1 replica from each shard for the SolrCloud setup to work for you. When you kill 1 shard, you essentially are taking away 1/3 of the range of shard key. On Sat, Jun 22, 2013 at 4:31 PM, Utkarsh Sengar wrote: > Hello, > > I am testing a 3 node solrcloud cluster with 3 sh

Re: solrcloud 4.3.1 - stability and failure scenario questions

2013-06-22 Thread Utkarsh Sengar
Just to be clear here, I when I say "I killed a node". I just killed the solr process on that node. zk on all the 3 nodes were still running. Thanks, -Utkarsh On Sat, Jun 22, 2013 at 4:01 AM, Utkarsh Sengar wrote: > Hello, > > I am testing a 3 node solrcloud cluster with 3 shards. 3 zk nodes ar

solrcloud 4.3.1 - stability and failure scenario questions

2013-06-22 Thread Utkarsh Sengar
Hello, I am testing a 3 node solrcloud cluster with 3 shards. 3 zk nodes are running in a different process in the same machines. I wanted to know the recommended size of a solrcloud cluster (min zk nodes?) This is the SolrCloud dump: https://gist.github.com/utkarsh2012/5840455 And, I am not su