Here's a blog I wrote up a bit ago: http://searchhub.org/2013/08/23/understanding-transaction-logs-softcommit-and-commit-in-sorlcloud/
Hmmm, unfortunately it doesn't say anything about how to set the fsync option, but do you really care? Soft commits flush to the op system, so a JVM crash/termination shouldn't affect it anyway. Turning on the fsync would just be a little bit of extra protection.... On Tue, Aug 27, 2013 at 11:43 AM, Sandro Zbinden <zbin...@imagic.ch> wrote: > Hey Mark > > Thank you very much for the quick answer. We have a single node > environment. > > I try to find the fsync option but was not successful. Ended up in the > UpdateLog class :-) > > How do I enable fsync in the solrconfig.xml ? > > > Besides that: > > If solr soft commit feature has a on disk guarantee with a transaction log > why we don't use solr soft commit as the default commit option ? > > > -----Ursprüngliche Nachricht----- > Von: Mark Miller [mailto:markrmil...@gmail.com] > Gesendet: Dienstag, 27. August 2013 17:12 > An: solr-user@lucene.apache.org > Betreff: Re: Transaction log "on-disk" guarantees > > > On Aug 27, 2013, at 11:08 AM, Sandro Zbinden <zbin...@imagic.ch> wrote: > > > Can we activate the transaction log to have on disk guarantees and then > use the solr soft commit feature ? > > Yes you can. If you only have a single node (no replication), you probably > want to turn on fsync via the config. > > - Mark > >
