cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3125) Move gossip library into a standalone artifact
Date Wed, 06 Mar 2013 17:52:14 GMT


Brandon Williams commented on CASSANDRA-3125:

It's not easy by any means.  First, cassandra historically makes heavy use of singletons,
and the gossiper is one of those.  You can't even instantiate two gossipers in the same JVM
right now.  Second, it needs to call into other singletons, like StorageService to know if
a node is a ring member or not. Finally, states in both ApplicationState and DEAD_STATES would
need to be abstracted and probably passed in with dependency injection, but those reach deep
into SS and others as well, so basically you have to do everything as a whole, which doesn't
just mean the singleton removal, but a global context manager of some sort, and a lot of interfaces
if you actually want to make it reusable.

All of that said, I know how this can be done, but it's a huge amount of work, and I'd prefer
to do it near(ish) the end of a release cycle, otherwise merging is going to be *constantly*
> Move gossip library into a standalone artifact 
> -----------------------------------------------
>                 Key: CASSANDRA-3125
>                 URL:
>             Project: Cassandra
>          Issue Type: Task
>            Reporter: Jake Farrell
>            Priority: Minor
>              Labels: gsoc, gsoc2012, mentor
> There has been some talk on the mailing list of people want to use the gossip portion
of cassandra in their own applications. The goal for this will be to create a standalone artifact

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message