Re: Real Time indexing and Scalability

2015-06-05 Thread Amit Jha
Thanks everyone. I got the answer. Rgds AJ > On Jun 6, 2015, at 7:00 AM, Erick Erickson wrote: > > bq: if 2 servers are master that means writing can be done on both. > > If there's a single piece of documentation that supports this contention, > we'll correct it immediately. But it's simply n

Re: Real Time indexing and Scalability

2015-06-05 Thread Erick Erickson
bq: if 2 servers are master that means writing can be done on both. If there's a single piece of documentation that supports this contention, we'll correct it immediately. But it's simply not true. As Shawn says, the entire design behind master/slave architecture is that there is exactly one (and

Re: Real Time indexing and Scalability

2015-06-05 Thread Shawn Heisey
On 6/5/2015 2:20 PM, Amit Jha wrote: > Thanks Shawn, for reminding CloudSolrServer, yes I have moved to SolrCloud. > > I agree that repeater is a slave and acts as master for other slaves. But > still it's a master and logically it has to obey the what master suppose to > obey. > > if 2 servers

Re: Real Time indexing and Scalability

2015-06-05 Thread Amit Jha
Thanks Shawn, for reminding CloudSolrServer, yes I have moved to SolrCloud. I agree that repeater is a slave and acts as master for other slaves. But still it's a master and logically it has to obey the what master suppose to obey. if 2 servers are master that means writing can be done on both

Re: Real Time indexing and Scalability

2015-06-05 Thread Shawn Heisey
On 6/5/2015 1:38 PM, Amit Jha wrote: > Thanks Eric, what about document is committed to master?Then document should > be visible from master. Is that correct? > > I was using replication with repeater mode because LBHttpSolrServer can send > write request to any of the Solr server, and that Solr

Re: Real Time indexing and Scalability

2015-06-05 Thread Amit Jha
Thanks Eric, what about document is committed to master?Then document should be visible from master. Is that correct? I was using replication with repeater mode because LBHttpSolrServer can send write request to any of the Solr server, and that Solr should index the document because it a master

Re: Real Time indexing and Scalability

2015-06-05 Thread Erick Erickson
You have to provide a _lot_ more details. You say: "The problem... some data was not get indexed... still sometime we found that documents are not getting indexed". Neither of these should be happening, so I suspect 1> you're expectations aren't correct. For instance, in the master/slave setup you

Re: Real Time indexing and Scalability

2015-06-05 Thread Amit Jha
I want to have realtime index and realtime search. Rgds AJ > On Jun 5, 2015, at 10:12 PM, Amit Jha wrote: > > Hi, > > In my use case, I am adding a document to Solr through spring application > using spring-data-solr. This setup works well with single Solr. In current > setup it is single po

Real Time indexing and Scalability

2015-06-05 Thread Amit Jha
Hi, In my use case, I am adding a document to Solr through spring application using spring-data-solr. This setup works well with single Solr. In current setup it is single point of failure. So we decided to use solr replication because we also need centralized search. Therefore we setup two ins