[
https://issues.apache.org/jira/browse/SOLR-3658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13419514#comment-13419514
]
Mark Miller commented on SOLR-3658:
-----------------------------------
SolrCmdDIstributor is using a thread executor that has no bounds on the number
of threads it can create. Commit or busy activity on a replica can cause a
small backup that leads to spikes of threads on the leader. They tend to spike
up and then come back down. Since each thread eats memory, this can be very
costly or cause an OOME: cant create new native thread.
One possible workaround is to lower the thread stack size - on many 64-bit
platforms it defaults to 1mb...-Xss=128kb might be enough and might make the
situation better. It's not a solution though.
As a fix, after discussing with Yonik, I've been working on limiting the number
of threads to 8 x the number of hosts in the cluster as a start. Perhaps it
will be overridable with config.
> SolrCmdDistributor can briefly create spikes of threads in the thousands.
> -------------------------------------------------------------------------
>
> Key: SOLR-3658
> URL: https://issues.apache.org/jira/browse/SOLR-3658
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Reporter: Mark Miller
> Assignee: Mark Miller
> Fix For: 4.0, 5.0
>
>
> see mailing list http://markmail.org/thread/yy5b7g6g7733wgcp
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
