On 1/23/2014 11:01 AM, Software Dev wrote:
Is there any way to configure autoCommit, softCommit values on a per
request basis? The majority of the time we have small flow of updates
coming in and we would like to see them in ASAP. However we occasionally
need to do some bulk indexing (once a week or less) and the need to see
those updates right away isn't as critical.
I would say 95% of the time we are in "Index-Light Query-Light/Heavy" mode
and the other 5% is "Index-Heavy Query-Light/Heavy" mode.
One thing missing on that searchhub page is the commitWithin parameter.
This is a parameter that will ensure that any documents added by that
update request will be committed within the number of milliseconds
given. This is particularly useful for bursty updates, because if all
your updates are done before the commitWithin time expires, a single
commit will get all of them, not just the first one.
http://wiki.apache.org/solr/CommitWithin
Since Solr 4.0, commitWithin will result in a soft commit. With 4.2 and
later, it can optionally be changed to a hard commit.
https://issues.apache.org/jira/browse/SOLR-4370
If you're using SolrCloud with a distributed index, some versions may
not work as expected when using commitWithin:
https://issues.apache.org/jira/browse/SOLR-5658
Thanks,
Shawn
