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 2016/04/27 17:59:13 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=15260368#comment-15260368 ]
Brandon Williams commented on CASSANDRA-10745:
----------------------------------------------
I think if people want to continue using PFS, that's fine. I think the best step we can take here is making GPFS not be PFS-compatible unless a -D flag is passed. This way we're optimized for the new cluster with GPFS case, instead of the migration case, since the latter is likely in the minority now.
> 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)