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 won't see docs on the slave until after the polling interval is expired and the index is replicated. 2> In SolrCloud you aren't committing appropriately. You might review: http://wiki.apache.org/solr/UsingMailingLists Best, Erick On Fri, Jun 5, 2015 at 9:45 AM, Amit Jha <shanuu....@gmail.com> wrote: > I want to have realtime index and realtime search. > > Rgds > AJ > >> On Jun 5, 2015, at 10:12 PM, Amit Jha <shanuu....@gmail.com> 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 point of failure. So we decided to use solr replication >> because we also need centralized search. Therefore we setup two instances >> both in repeater mode. The problem with this setup was, some time data was >> not get indexed. So we moved to SolrCloud, with 3zk and 2 shards and 2 >> replica setup, but still sometime we found that documents are not getting >> indexed. >> >> I would like to know what is the best way to have highly available setup. >> >> Rgds >> AJ
