Inline quoting ahead, sorry:
Colin:
Stop. Back up. The automatic soft commits will make updates available to
your users every second. Those documents _include_ anything from your "hard
commit" jobs. What could be faster? Parenthetically I'll add that 1 second
soft commits are rarely an actual r
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
On 02/17/2014 09:46 PM, Shawn Heisey wrote:
I think I put too much information in my reply. Apologies. Here's the
most important information to deal with first:
Don't send hard commits at all. Configure autoCommit in your server
config, with the all-important openSearcher parameter set to fal
On 02/17/2014 05:38 PM, Shawn Heisey wrote:
On 2/17/2014 6:06 PM, Colin Bartolome wrote:
We're using Solr version 4.2.1, in case new functionality has helped
with this issue.
We have our Solr servers doing automatic soft commits with maxTime=1000.
We also have a scheduled job that trigg
We're using Solr version 4.2.1, in case new functionality has helped with
this issue.
We have our Solr servers doing automatic soft commits with maxTime=1000.
We also have a scheduled job that triggers a hard commit every fifteen
minutes. When one of these hard commits happens while a soft com
