On 8/13/2021 7:36 AM, Reej M wrote:
Have any of you found a solution for the Task Queue processing has stalled
for 20077 ms with 0 remaining elements to process.
We are using solr 8.8.2, randomly we get this error while indexing. Is there
any way we need to tune the solr.autocommit.maxtime?
For few cores we have it as 15000, for few we have it as 500, 1 or -1. Also
the maxwarmingsearchers is set to 2
Kindly advise on how to tune this.
A value of 500 or 1 is far too aggressive. It means that a commit will
fire off either half a second or one millisecond after any updates are
made. A value of -1 turns the feature off and you do not want that.
The example configs have it set to 15000 (15 seconds), I personally
would go with 60000. And I would make sure that openSearcher is set to
false on autoCommit. That option on autoSoftCommit makes no sense, so
you won't find it in example configs. For autoSoftCommit the maxTime
value should be much larger -- two minutes (120000) is about as low as I
would dare go on that.
I don't know that any autoCommit setting is going to help with that
particular message, though. The message was added to 8.4 by this issue:
https://issues.apache.org/jira/browse/SOLR-13975
With version before 8.4, the stall would still occur but you would not
be notified, and it would probably stall forever -- 8.4 can apparently
break the stall.
As for what might be causing it, I do not know. It might be that your
heap is too small, causing Java to spend a lot of time doing garbage
collection in order to keep Solr running. Or it might be a general
performance issue. If you can provide your GC logs that Solr writes, I
can look into the possibility of garbage collection pauses. You'll need
to put them on a file sharing site and provide links -- the mailing list
eats message attachments.
Thanks,
Shawn
