I suggest you to read here: http://searchhub.org/2013/08/23/understanding-transaction-logs-softcommit-and-commit-in-sorlcloud/
Thanks; Furkan KAMACI 2013/11/24 Mark Miller <markrmil...@gmail.com> > SolrCloud does not use commits for update acceptance promises. > > The idea is, if you get a success from the update, it’s in the system, > commit or not. > > Soft Commits are used for visibility only. > > Standard Hard Commits are used essentially for internal purposes and > should be done via auto commit generally. > > To your question though - it is fine to send a commit while updates are > coming in from another source - it’s just not generally necessary to do > that anyway. > > - Mark > > On Nov 24, 2013, at 1:01 PM, adfel70 <adfe...@gmail.com> wrote: > > > Hi everyone, > > > > I am wondering how commit operation works in SolrCloud: > > Say I have 2 parallel indexing processes. What if one process sends big > > update request (an add command with a lot of docs), and the other one > just > > happens to send a commit command while the update request is being > > processed. > > Is it possible that only part of the documents will be commited? > > What will happen with the other docs? Is Solr transactional and promise > that > > there will be no partial results? > > > > > > > > -- > > View this message in context: > http://lucene.472066.n3.nabble.com/Commit-behaviour-in-SolrCloud-tp4102879.html > > Sent from the Solr - User mailing list archive at Nabble.com. > >
