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

Mark Miller commented on SOLR-2358:
-----------------------------------

bq. Should another issue be opened for the tests?

I have another issue for the test problem: SOLR-3066

bq. Do the failures reproduce if you ssh into the hudson machine itself and 
test from there?

I can't currently get into the hudson machine - used the wrong username the 
other day and seemed to get ip banned pretty much right away. Looking into 
getting that undone.

bq. Do any tests rely upon not being able to connect to a tcp/udp port

Sometimes, yes - because jetties are going up and down during these tests, 
sometimes you wouldn't be able to connect - I wouldn't say we rely on it, but 
it seems it could happen. 

bq. unless you do some tricks.

Which tricks? This could be part of it by the sound of things.
                
> Distributing Indexing
> ---------------------
>
>                 Key: SOLR-2358
>                 URL: https://issues.apache.org/jira/browse/SOLR-2358
>             Project: Solr
>          Issue Type: New Feature
>          Components: SolrCloud, update
>            Reporter: William Mayor
>            Priority: Minor
>             Fix For: 4.0
>
>         Attachments: 2shard4server.jpg, SOLR-2358.patch, SOLR-2358.patch, 
> apache-solr-noggit-r1211150.jar, zookeeper-3.3.4.jar
>
>
> The indexing side of SolrCloud - the goal of this issue is to provide 
> durable, fault tolerant indexing to an elastic cluster of Solr instances.

--
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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to