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

Mark Miller commented on SOLR-3932:
-----------------------------------

I'm not sure what the heck is on the other end of these socket read hangs - the 
stack trace indicates it could only be jetty?

I've tried a variety of settings in both jetty and httpclient to how this 
changes - I did find that if i drop max connections per host in http client to 
2 or 3, I don't seem to see the issue.

Also, only allowing like 2 httpclients to fire at a time (rather than the 
default of 8 per host), seemed to make the issue go away or happen much less 
frequently.

Both options would seem to simply decrease the load...

I'm not sure what is up yet - I've also tried upgrading httpclient/components - 
but no luck.
                
> SolrCmdDistributorTest either takes 3 seconds or 3 minutes.
> -----------------------------------------------------------
>
>                 Key: SOLR-3932
>                 URL: https://issues.apache.org/jira/browse/SOLR-3932
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud, Tests
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>             Fix For: 4.1, 5.0
>
>
> I've looked into this a little in the past, but had not come to a conclusion. 
> It really bugs me because it doubles my test run time from 3 minutes to 6 
> minutes when it happens.
> I've been looking into it today and I think I've tracked the problem down to 
> mostly test bugs. One real bug around distrib commit ordering was also 
> uncovered.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to