cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-3120) Move RING_DELAY and operations that use it to Gossiper
Date Thu, 01 Mar 2012 12:52:00 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-3120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Brandon Williams resolved CASSANDRA-3120.
-----------------------------------------

    Resolution: Not A Problem

Closing as this was better solved by CASSANDRA-3600
                
> Move RING_DELAY and operations that use it to Gossiper
> ------------------------------------------------------
>
>                 Key: CASSANDRA-3120
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3120
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Brandon Williams
>            Assignee: Brandon Williams
>            Priority: Minor
>
> RING_DELAY more appropriately belongs to Gossiper, rather than SS.  SS has a history
of not respecting it correctly (such as CASSANDRA-2072) so we should confine it to the Gossiper,
and have SS call methods on the Gossiper where needed.  Currently we're allowing delays to
be passed in some instances to the Gossiper in order to cheat RING_DELAY for tests so we don't
have to wait the full delay.  Instead we can use a special constructor on the Gossiper that
is only used in tests.

--
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

        

Mime
View raw message