You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cassandra.apache.org by Roland Gude <ro...@yoochoose.com> on 2011/09/02 12:05:13 UTC

AW: interest in creating a "cassandra-gossip" library?

Hi,

Is there any progress on this topic?
I would really like to see such a library.

-----Ursprüngliche Nachricht-----
Von: matthew hawthorne [mailto:mhawthorne@gmail.com] 
Gesendet: Mittwoch, 22. Dezember 2010 20:07
An: dev@cassandra.apache.org
Betreff: interest in creating a "cassandra-gossip" library?

hello,

I'm starting a project at my day job to deploy a gossip protocol
implementation.  part of my initial work is to evaluate existing
implementations.

being loosely familiar with Cassandra, I read
http://wiki.apache.org/cassandra/ArchitectureGossip and have looked
over the related code a bit.

is there interest in breaking out the gossip-related portions of
Cassandra into a library that could be reused by other projects?  I
work on a team that is ready and willing to contribute heavily.  we'd
just need some guidance as to how to structure the Cassandra
subcomponent(s) and properly integrate them with the builds, tests,
etc.

here are a few examples of functionality we're looking to add:

1) hierarchical state - our use case is cross data center gossip,
where we don't want every node in the 2 clusters communicating, but do
want a node from cluster1 to send a summary of the cluster's state to
cluster2, and vice versa.  essentially I'm talking about rolling up
the state of multiple nodes into a single "virtual" node

2) mutual authentication - nodes verifying the identity of other nodes
before gossipping

3) encryption - encrypted traffic, especially for the cross data center case

any opinions on this? thanks in advance for any feedback!

-matt


Re: AW: interest in creating a "cassandra-gossip" library?

Posted by Edward Capriolo <ed...@gmail.com>.
Would this help?
http://svn.apache.org/viewvc?view=revision&revision=1157967

On Fri, Sep 2, 2011 at 10:01 AM, Jake Farrell <jf...@apache.org> wrote:

> Roland, I was also interested in this for very similar reasons. I was
> planning on working on this after tackling some of the thrift build clean
> and transport requests i've been working on. I created CASSANDRA-3125 to
> help track the progress of this a little easier
>
> -Jake
>
> On Sep 2, 2011, at 5:05 AM, Roland Gude wrote:
>
> > Hi,
> >
> > Is there any progress on this topic?
> > I would really like to see such a library.
> >
> > -----Ursprüngliche Nachricht-----
> > Von: matthew hawthorne [mailto:mhawthorne@gmail.com]
> > Gesendet: Mittwoch, 22. Dezember 2010 20:07
> > An: dev@cassandra.apache.org
> > Betreff: interest in creating a "cassandra-gossip" library?
> >
> > hello,
> >
> > I'm starting a project at my day job to deploy a gossip protocol
> > implementation.  part of my initial work is to evaluate existing
> > implementations.
> >
> > being loosely familiar with Cassandra, I read
> > http://wiki.apache.org/cassandra/ArchitectureGossip and have looked
> > over the related code a bit.
> >
> > is there interest in breaking out the gossip-related portions of
> > Cassandra into a library that could be reused by other projects?  I
> > work on a team that is ready and willing to contribute heavily.  we'd
> > just need some guidance as to how to structure the Cassandra
> > subcomponent(s) and properly integrate them with the builds, tests,
> > etc.
> >
> > here are a few examples of functionality we're looking to add:
> >
> > 1) hierarchical state - our use case is cross data center gossip,
> > where we don't want every node in the 2 clusters communicating, but do
> > want a node from cluster1 to send a summary of the cluster's state to
> > cluster2, and vice versa.  essentially I'm talking about rolling up
> > the state of multiple nodes into a single "virtual" node
> >
> > 2) mutual authentication - nodes verifying the identity of other nodes
> > before gossipping
> >
> > 3) encryption - encrypted traffic, especially for the cross data center
> case
> >
> > any opinions on this? thanks in advance for any feedback!
> >
> > -matt
> >
>
>

Re: AW: interest in creating a "cassandra-gossip" library?

Posted by Jake Farrell <jf...@apache.org>.
Roland, I was also interested in this for very similar reasons. I was planning on working on this after tackling some of the thrift build clean and transport requests i've been working on. I created CASSANDRA-3125 to help track the progress of this a little easier

-Jake

On Sep 2, 2011, at 5:05 AM, Roland Gude wrote:

> Hi,
> 
> Is there any progress on this topic?
> I would really like to see such a library.
> 
> -----Ursprüngliche Nachricht-----
> Von: matthew hawthorne [mailto:mhawthorne@gmail.com] 
> Gesendet: Mittwoch, 22. Dezember 2010 20:07
> An: dev@cassandra.apache.org
> Betreff: interest in creating a "cassandra-gossip" library?
> 
> hello,
> 
> I'm starting a project at my day job to deploy a gossip protocol
> implementation.  part of my initial work is to evaluate existing
> implementations.
> 
> being loosely familiar with Cassandra, I read
> http://wiki.apache.org/cassandra/ArchitectureGossip and have looked
> over the related code a bit.
> 
> is there interest in breaking out the gossip-related portions of
> Cassandra into a library that could be reused by other projects?  I
> work on a team that is ready and willing to contribute heavily.  we'd
> just need some guidance as to how to structure the Cassandra
> subcomponent(s) and properly integrate them with the builds, tests,
> etc.
> 
> here are a few examples of functionality we're looking to add:
> 
> 1) hierarchical state - our use case is cross data center gossip,
> where we don't want every node in the 2 clusters communicating, but do
> want a node from cluster1 to send a summary of the cluster's state to
> cluster2, and vice versa.  essentially I'm talking about rolling up
> the state of multiple nodes into a single "virtual" node
> 
> 2) mutual authentication - nodes verifying the identity of other nodes
> before gossipping
> 
> 3) encryption - encrypted traffic, especially for the cross data center case
> 
> any opinions on this? thanks in advance for any feedback!
> 
> -matt
>