You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sean Durity (JIRA)" <ji...@apache.org> on 2015/12/14 22:02:46 UTC
[jira] [Commented] (CASSANDRA-10745) Deprecate PropertyFileSnitch
[ https://issues.apache.org/jira/browse/CASSANDRA-10745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15056714#comment-15056714 ]
Sean Durity commented on CASSANDRA-10745:
-----------------------------------------
I would not want to use GPFS. PropertyFileSnitch is easier to package and distribute because I can include the exact same file for every host. GPFS requires that files are (potentially) different on every host. Also, if I am on any particular host, I can view the full topology in the topology file. So, not a use case argument, exactly, but I would have to write logic to create the GPFS file on each node during deployment. Guess what I would include? Something very like the topology file.
> Deprecate PropertyFileSnitch
> ----------------------------
>
> Key: CASSANDRA-10745
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10745
> Project: Cassandra
> Issue Type: Improvement
> Components: Coordination, Distributed Metadata
> Reporter: Paulo Motta
> Priority: Minor
>
> Opening this ticket to discuss deprecating PropertyFileSnitch, since it's error-prone and more snitch code to maintain (See CASSANDRA-10243). Migration from existing cluster with PropertyFileSnitch to GossipingPropertyFileSnitch is straightforward.
> Is there any useful use case that can be achieved only with PropertyFileSnitch?
> If not objections, we would add deprecation warnings in 2.2.x, 3.0.x, 3.2 and deprecate in 3.4 or 3.6.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)