[
https://issues.apache.org/jira/browse/CASSANDRA-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Greene updated CASSANDRA-282:
-------------------------------------
Attachment: 282-v1.diff
This patch shifts all the relevant ports by 10, so they are still predictable.
It also sets the timeout for a new client connection to 10 seconds, because 20
seconds gets really unreasonable if you are trying to debug things, and I can't
imagine the regression test server taking longer than 10 seconds to come up.
> system tests fail straingely if an instance is running
> ------------------------------------------------------
>
> Key: CASSANDRA-282
> URL: https://issues.apache.org/jira/browse/CASSANDRA-282
> Project: Cassandra
> Issue Type: Bug
> Reporter: Eric Evans
> Assignee: Eric Evans
> Attachments: 282-v1.diff
>
>
> The system tests blow up spectacularly if there is another instance of
> cassandra running (and it can be difficult to tell that this is why). Having
> the harness start its instance using alternate ports would prevent this from
> happening in some cases, but something should be done to test for instances
> left over from failed tests, and at least produce clearer error messages.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
