You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@lucene.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/01/11 15:07:39 UTC

[jira] [Commented] (SOLR-8533) Raise default maxUpdateConnections and maxUpdateConnectionsPerHost to 100k each.

    [ https://issues.apache.org/jira/browse/SOLR-8533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15091935#comment-15091935 ] 

ASF subversion and git services commented on SOLR-8533:
-------------------------------------------------------

Commit 1724030 from [~markrmiller@gmail.com] in branch 'dev/trunk'
[ https://svn.apache.org/r1724030 ]

SOLR-8533: Raise default maxUpdateConnections and maxUpdateConnectionsPerHost to 100k each.

> Raise default maxUpdateConnections and maxUpdateConnectionsPerHost to 100k each.
> --------------------------------------------------------------------------------
>
>                 Key: SOLR-8533
>                 URL: https://issues.apache.org/jira/browse/SOLR-8533
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>
> The current default are still too low for a large cluster and it's difficult to diagnose the issues when hitting these limits (there is also not really not much you can do but raise them). With the current thread model we use, we need to just raise these limits up very high.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org