cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (CASSANDRA-1974) PFEPS-like snitch that uses gossip instead of a property file
Date Tue, 09 Aug 2011 16:06:27 GMT

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

Jonathan Ellis reassigned CASSANDRA-1974:
-----------------------------------------

    Assignee:     (was: Brandon Williams)

I think the biggest win is when you can automatically determine rack/dc from the environment
somehow (e.g.: ec2snitch).  Otherwise the advantage of editing a file, vs edit + rsync, is
small.  Small enough that it's probably not worth the education headache.

> PFEPS-like snitch that uses gossip instead of a property file
> -------------------------------------------------------------
>
>                 Key: CASSANDRA-1974
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1974
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Brandon Williams
>            Priority: Minor
>
> Now that we have an ec2 snitch that propagates its rack/dc info via gossip from CASSANDRA-1654,
it doesn't make a lot of sense to use PFEPS where you have to rsync the property file across
all the machines when you add a node.  Instead, we could have a snitch where you specify its
rack/dc in a property file, and propagate this via gossip like the ec2 snitch.  In order to
not break PFEPS, this should probably be a new snitch.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message