You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (JIRA)" <ji...@apache.org> on 2011/01/12 20:24:45 UTC
[jira] Created: (CASSANDRA-1974) PFEPS-like snitch that uses gossip
instead of a property file
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
Affects Versions: 0.7.0
Reporter: Brandon Williams
Assignee: Brandon Williams
Fix For: 0.7.1
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.
-
You can reply to this email to add a comment to the issue online.
[jira] [Assigned] (CASSANDRA-1974) PFEPS-like snitch that uses
gossip instead of a property file
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (CASSANDRA-1974) PFEPS-like snitch that uses
gossip instead of a property file
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (CASSANDRA-1974) PFEPS-like snitch that uses
gossip instead of a property file
Posted by "Brandon Williams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brandon Williams updated CASSANDRA-1974:
----------------------------------------
Fix Version/s: (was: 0.8.4)
> 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
>
> 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
[jira] [Assigned] (CASSANDRA-1974) PFEPS-like snitch that uses
gossip instead of a property file
Posted by "Brandon Williams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brandon Williams reassigned CASSANDRA-1974:
-------------------------------------------
Assignee: Brandon Williams
> 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
>
> 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.
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
[jira] [Commented] (CASSANDRA-1974) PFEPS-like snitch that uses
gossip instead of a property file
Posted by "Vijay (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13283639#comment-13283639 ]
Vijay commented on CASSANDRA-1974:
----------------------------------
+1
> 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
> Attachments: 1974.txt
>
>
> 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.
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
[jira] [Updated] (CASSANDRA-1974) PFEPS-like snitch that uses
gossip instead of a property file
Posted by "Brandon Williams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brandon Williams updated CASSANDRA-1974:
----------------------------------------
Reviewer: vijay2win@yahoo.com
> 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
> Attachments: 1974.txt
>
>
> 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.
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
[jira] [Commented] (CASSANDRA-1974) PFEPS-like snitch that uses
gossip instead of a property file
Posted by "Wilfried Schobeiri (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13276841#comment-13276841 ]
Wilfried Schobeiri commented on CASSANDRA-1974:
-----------------------------------------------
For those of us not on ec2, it would be incredibly convenient to have changes to the topology propagate across the entire cluster instead of maintaining an additional rsync. +1
> 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.
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
[jira] Commented: (CASSANDRA-1974) PFEPS-like snitch that uses
gossip instead of a property file
Posted by "Brandon Williams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980875#action_12980875 ]
Brandon Williams commented on CASSANDRA-1974:
---------------------------------------------
I think when adding a node it's easier to specify once and then bootstrap rather than rsync it everywhere. And you'd only have 100 separate files if you had 100 DCs/racks.
> 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
> Affects Versions: 0.7.0
> Reporter: Brandon Williams
> Assignee: Brandon Williams
>
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] [Updated] (CASSANDRA-1974) PFEPS-like snitch that uses
gossip instead of a property file
Posted by "Brandon Williams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brandon Williams updated CASSANDRA-1974:
----------------------------------------
Attachment: 1974.txt
Adds a GossipingPropertyFileSnitch that enables defining the local node's rack/dc in cassandra-rackdc.properties and propagating that via gossip, while still utilizing PFS as a fallback if cassandra-topologies.properties is present, allowing migration from PFS to GPFS.
> 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
> Attachments: 1974.txt
>
>
> 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.
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
[jira] Updated: (CASSANDRA-1974) PFEPS-like snitch that uses gossip
instead of a property file
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-1974:
--------------------------------------
Fix Version/s: (was: 0.7.1)
Is it really easier to keep 100 separate files correct, than a single one?
> 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
> Affects Versions: 0.7.0
> Reporter: Brandon Williams
> Assignee: Brandon Williams
>
> 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.
-
You can reply to this email to add a comment to the issue online.