lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From SolrLover <bbar...@gmail.com>
Subject How to make soft commit more reliable?
Date Tue, 23 Jul 2013 22:56:58 GMT
Currently I am using SOLR 3.5.X and I push updates to SOLR via queue (Active
MQ) and perform hard commit every 30 minutes (since my index is relatively
big around 30 million documents). I am thinking of using soft commit to
implement NRT search but I am worried about the reliability.

For ex: If I have the hard autocommit set to 10 minutes and a softcommit
every second, new documents will show up every second but in case of JVM
crash or power goes out I will lose all the documents after the last hard
commit. 

I was thinking of using a backup database or another SOLR index that I can
use as a backup and write the document from queue in both places (one with
soft commit, another index with just the push updates with normal hard
commits (or) write simultaneously to a db and delete the rows once the hard
commit is successful after making sure that we didn't lose any records).

Does someone have any other idea to improve the reliability of the push
updates when using soft commit?




--
View this message in context: http://lucene.472066.n3.nabble.com/How-to-make-soft-commit-more-reliable-tp4079892.html
Sent from the Solr - User mailing list archive at Nabble.com.

Mime
View raw message