[jira] [Commented] (SOLR-5741) UpdateShardHandler not setting max connections correctly

["Shawn Heisey (JIRA)" <ji...@apache.org>]

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

Shawn Heisey commented on SOLR-5741:
------------------------------------

I'm inclined to go ahead and commit this to 4x and trunk, but I'd like a sanity check.  This might explain some recent problems people have been having with sending lots of updates to large clouds.


> UpdateShardHandler not setting max connections correctly
> --------------------------------------------------------
>
>                 Key: SOLR-5741
>                 URL: https://issues.apache.org/jira/browse/SOLR-5741
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud, update
>    Affects Versions: 4.6.1
>            Reporter: Shawn Heisey
>              Labels: patch
>             Fix For: 4.7, 5.0
>
>         Attachments: SOLR-5741.patch
>
>
> The following line in UpdateShardHandler.java looks incorrect to me:
> {code}
> clientConnectionManager.setDefaultMaxPerRoute(cfg.getMaxUpdateConnections());
> {code}
> I think it should be:
> {code}
> clientConnectionManager.setMaxTotal(cfg.getMaxUpdateConnections());
> {code}



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

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