5.3.0 Read Time Outs
+1 to what Shalin said. You've adjusted maxWarmingSeachers up,
probably because you saw warnings in the log files. This is _not_ the solution
to the "MaxWarmingSearchers exceeded" error. The solution is, as Shalin says,
decrease your commit frequency.
C
+1 to what Shalin said. You've adjusted maxWarmingSeachers up,
probably because you saw warnings in the log files. This is _not_
the solution to the "MaxWarmingSearchers exceeded" error. The solution
is, as Shalin says, decrease your commit frequency.
Commit can be an expensive operation,
see:
ht
Yes, that is probably the cause. I think you have very aggressive
commit rates and Solr is not able to keep up. If you are sending
explicit commits, switch to using autoCommit with openSearcher=false
every 5-10 minutes (this depends on your indexing rate) and
autoSoftCommit every 2-5 minutes. Adjus
Hi there,
I am using Solr Cloud 5.3.0 on a multiserver cluster (3 servers to mention)
whereby each server spec is at 16 core and 32 GB Ram.
I am facing regular errors - Error sending update to http://someip:8983/solr
- "Timeout occured while waiting response from server at server a" ... Caus
