On 02/18/2014 10:15 AM, Shawn Heisey wrote:
If you want to be completely in control like that, get rid of the
automatic soft commits and just do the hard commits.
I would personally choose another option for your setup -- get rid of
*all* explicit commits entirely, and just configure autoCommit and
autoSoftCommit in the server config. Since you're running 4.x, you really
should have the transaction log (updateLog in the config) enabled. You
can rely on the transaction log to replay updates since the last hard
commit if there's ever a crash.
I would also recommend upgrading to 4.6.1, but that's a completely
separate item.
Thanks,
Shawn
We use the automatic soft commits to get search index updates to our users
faster, via Near Realtime Searching. We have the updateLog enabled. I'm
not worried that the Solr side of the equation will lose data; I'm worried
that the communication from our web servers and scheduled jobs to the Solr
servers will break down and nothing will come along to make sure
everything is up to date. It sounds like what we're picturing is not
currently supported, so I'll file the RFE.
Will upgrading to 4.6.1 help at all with this issue?
