You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2011/06/16 00:08:47 UTC

[jira] [Updated] (CASSANDRA-1974) PFEPS-like snitch that uses gossip instead of a property file

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

Jonathan Ellis updated CASSANDRA-1974:
--------------------------------------

             Priority: Minor  (was: Major)
    Affects Version/s:     (was: 0.7.0)
        Fix Version/s: 0.8.2

> 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
>            Assignee: Brandon Williams
>            Priority: Minor
>             Fix For: 0.8.2
>
>
> 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