[ https://issues.apache.org/jira/browse/SOLR-9253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15353558#comment-15353558 ]
Shalin Shekhar Mangar commented on SOLR-9253: --------------------------------------------- bq. Before hitting a critical failure, would there be any indications in the logs of the possible need to increase the pool? Issuing a warning might be useful when lease times exceed a certain threshold. If a sane connection timeout has been specified then there should be ConnectionPoolTimeoutException wrapped inside a RequestAbortedException. AFAIK, the lease times aren't available to us. The PoolingHttpClientConnectionManager exposes pool statistics but we don't expose that anywhere. > solrcloud goes dowm > ------------------- > > Key: SOLR-9253 > URL: https://issues.apache.org/jira/browse/SOLR-9253 > Project: Solr > Issue Type: Wish > Security Level: Public(Default Security Level. Issues are Public) > Components: clients - java > Affects Versions: 4.9.1 > Environment: jboss, zookeeper > Reporter: Junfeng Mu > Attachments: 20160627161845.png, javacore.165.txt > > Original Estimate: 96h > Remaining Estimate: 96h > > We use solrcloud in our project. now we use solr, but the data grows bigger > and bigger, so we want to switch to solrcloud, however, once we switch to > solrcloud, solrcloud goes down, It seems that solrcloud blocked, can not deal > with the new query, please see the attachments and help us ASAP. Thanks! -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org