On 10/22/2018 9:44 PM, Clemens Wyss DEV wrote:
On 10/22/2018 6:15 AM, Shawn Heisey wrote:
autoSoftCommit is pretty aggressive . If your commits are taking 1-2 seconds or
les
well, some take minutes (re-index)!
Are you absolutely sure that you have commits taking that much time?
I'm not talking about indexing, just the commit. Indexing a big batch of
documents can take a while, but even on a huge index, commits shouldn't
take a super long time, unless your cache warming is excessive.
autoCommit is quite long. I'd probably go with 60 seconds
Which means every 1min the "pending"/"soft" commits are effectively saved?
One additional question: having auto(soft)commits in place, do I at all need to
explicitly commit UpdateRequest from SolrJ?
With openSearcher set to false, the hard commits that autoCommit does do
NOT make changes visible. A hard commit flushes outstanding data to
disk and starts a new transaction log. If openSearcher is left at the
default of "true" then it would also open a new searcher, making changes
visible.
Hard commits are about durability, soft commits are about visibility.
If you have autoSoftCommit or use commitWithin, you do not need to send
explicit commits.
I see that Shalin has replied with info about his work on the class
you're concerned about.
Thanks,
Shawn
