Re: Difference between softCommit and hardCommit?
On 1/9/13 2:47 PM, yayati wrote: curl 'http://server1:8983/solr/collection1/select?q=*:*' curl 'http://server2:7574/solr/collection1/select?q=*:*' Maybe you need to add distrib=true to your query? - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: Difference between softCommit and hardCommit?
Hi Mark, I have a query related to soft commit. This is my current setup same as example C of solrcloud wiki with embedded zookeeper running on 9983 only. numshard=2 Server1 : 2 solr instances running 8983(leader),8900(replica) Server2 : 2solr instance running 7574(leader),7500(replica). Now i added a document books.json to 8983 server with commit=false * http://localhost:8983/solr/update/json?stream.file=/SOLR-4/apache-solr-4.0.0/apache-solr-4.0.0/example/exampledocs/books.jsonstream.contentType=application/jsoncommit=false * Then did softcommit as follow : curl 'http://server1:8983/solr/update?softCommit=true' Now, i am getting strange outcome. On hitting this query multipie times i am getting different number of documents everytime. What could be reason for this. curl 'http://server1:8983/solr/collection1/select?q=*:*' curl 'http://server2:7574/solr/collection1/select?q=*:*' There are four documents in books.json. On hitting these queries again and again. Sometimes i get number of docs as 1, 3,4. Why result is not consistent. Ideally it shoudl return 4. As all nodes are up and healthy.(i.e green). Also, it would be great if you explain softcommit concept, it shows newly added document on query immediately. But is there is some difference if we do soft commit on replica not on leader?? and what if all servers go down and then up. This soft commit is lost or not? Thanks and then i did soft commit as follow : -- View this message in context: http://lucene.472066.n3.nabble.com/Difference-between-softCommit-and-hardCommit-tp4020425p4031865.html Sent from the Lucene - Java Developer mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Re: Difference between softCommit and hardCommit?
Hard commit is about persistence - you should usually use it with openSearcher=false now. It flushes deletes, calls fsync, ensures data is on stable storage. It also flushes the update log. Soft commit is about visibility. It does not flush deletes or call fsync. It opens a new Searcher from the Writer and is much faster. Soft commit is what allows for NRT (Near Realtime indexing). You can do it once a second or even faster if you really need to (though it will thrash your caches, so you only want to go as low as you need). We wanted to rename soft commit before 4, but we never got to it. - Mark On Thu, Nov 15, 2012 at 2:26 AM, Per Steffensen st...@designware.dk wrote: Hi Will anyone please explain the difference between softCommit and hardCommit (maybe just called commit)? Not only seen from the users perspective, but also a few technical details, please. Regards, Per Steffensen - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org -- - Mark - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
Difference between softCommit and hardCommit?
Hi Will anyone please explain the difference between softCommit and hardCommit (maybe just called commit)? Not only seen from the users perspective, but also a few technical details, please. Regards, Per Steffensen - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
