[
https://issues.apache.org/jira/browse/SOLR-2358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13195732#comment-13195732
]
Robert Muir commented on SOLR-2358:
-----------------------------------
{quote}
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.
{quote}
Yeah thats probably the best way to move forward. Otherwise you have to wait
like an hour just to see if one tweak to a single test worked.
{quote}
Which tricks? This could be part of it by the sound of things.
{quote}
It depends on what the test is doing, but just a few ideas:
* any client operations in tests should have a low connect()timeout/so_timeout.
if you always set this then it will never hang for long periods of time.
* if you absolutely need to test the case where you don't get a timeout but
another exception,
use an ipv6 test address (eg [ff01::114]). because jenkins has no ipv6, it
fails fast always. this won't work forever...
* in a situation where you have A talking to B, and you want to test a
condition where B goes down,
instead of just bringing B down, instead you can consider mocking up a remote
node to test failures.
bring up a "mock downed server" (e.g. just a ServerSocket on that same port
with reuseAddress=true).
this one can return whatever error you want, or just disconnect, and even
assert that A tried to
connect to it. maybe instead of using "real remote jettys" at all, most tests
could even be totally
implemented this way: it would be faster and simpler than spinning up so many
jettys in all the tests.
> 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]
