Thanks a lot, Shawn.
We'll consider your suggestion to tune our solr servers. Will let you know
the result.
Thanks!
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-has-a-CPU-spike-when-indexing-a-batch-of-data-tp4309529p4310002.html
Sent from the Solr - User ma
On 12/14/2016 1:28 AM, forest_soup wrote:
> We are doing index on the same http endpoint. But as we have shardnum=1 and
> replicafactor=1, so each collection only has one core. So there should no
> distributed update/query, as we are using solrj's CloudSolrClient which will
> get the target URL of
.
* How many collections are in each cloud?
80 collections with only one shard each. And replicafactor=1.
* How many servers are in each cloud?
5 solr nodes. So each solr node has 16 cores.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-has-a-CPU-spike-when-indexing-a-
On 12/13/2016 10:25 AM, Shawn Heisey wrote:
> That stacktrace indicates the thread is doing a query. If most of the
> threads have that stacktrace, it means Solr is handling a lot of
> simultaneous queries. That can cause a CPU spike. I checked one of the
> thread dumps
I didn't complete that sent
On 12/13/2016 6:09 AM, forest_soup wrote:
> I posted this issue to a JIRA. Could anyone help comment? Thanks!
>
> https://issues.apache.org/jira/browse/SOLR-9741
Please use the mailing list *before* opening an issue in Jira. If at
all possible, we want to be sure that problems are caused by a rea
Component.java:496)
at
org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:277)
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-has-a-CPU-spike-when-indexing-a-batch-of-data-tp4309529.html
Sent from the Solr - User mailing list archive at Nabble.com.
