You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Lance Weber (JIRA)" <ji...@apache.org> on 2009/08/21 05:46:14 UTC
[jira] Created: (CASSANDRA-390) Block connections on startup until
the ring is stabilized
Block connections on startup until the ring is stabilized
---------------------------------------------------------
Key: CASSANDRA-390
URL: https://issues.apache.org/jira/browse/CASSANDRA-390
Project: Cassandra
Issue Type: Improvement
Components: Core
Affects Versions: 0.4
Environment: Mac OSX
Reporter: Lance Weber
Priority: Minor
I'm seeing something strange and not quite repeatable. If I start up cassandra and then run my own unit tests shortly after startup, they'll fail read-write integrity assertions. But if I wait awhile - maybe a minute or so - and then run them they succeed.
jbellis indicated this may be a problem with the ring not being stabilized before requests are accepted
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CASSANDRA-390) Block connections on startup until
the ring is stabilized
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis resolved CASSANDRA-390.
--------------------------------------
Resolution: Won't Fix
There's no one-size-fits-all correct time to wait; e.g. our system tests or any other one-node system would prefer a wait time of zero; other systems will need time proportional to log(n) where n is the number of nodes.
I think we should leave this one to the individual ops teams.
> Block connections on startup until the ring is stabilized
> ---------------------------------------------------------
>
> Key: CASSANDRA-390
> URL: https://issues.apache.org/jira/browse/CASSANDRA-390
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Environment: Mac OSX
> Reporter: Lance Weber
> Priority: Minor
> Fix For: 0.5
>
>
> I'm seeing something strange and not quite repeatable. If I start up cassandra and then run my own unit tests shortly after startup, they'll fail read-write integrity assertions. But if I wait awhile - maybe a minute or so - and then run them they succeed.
> jbellis indicated this may be a problem with the ring not being stabilized before requests are accepted
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CASSANDRA-390) Block connections on startup until
the ring is stabilized
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-390:
-------------------------------------
Fix Version/s: 0.5
Affects Version/s: (was: 0.4)
> Block connections on startup until the ring is stabilized
> ---------------------------------------------------------
>
> Key: CASSANDRA-390
> URL: https://issues.apache.org/jira/browse/CASSANDRA-390
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Environment: Mac OSX
> Reporter: Lance Weber
> Priority: Minor
> Fix For: 0.5
>
>
> I'm seeing something strange and not quite repeatable. If I start up cassandra and then run my own unit tests shortly after startup, they'll fail read-write integrity assertions. But if I wait awhile - maybe a minute or so - and then run them they succeed.
> jbellis indicated this may be a problem with the ring not being stabilized before requests are accepted
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.