[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)
[jira] [Commented] (CASSANDRA-10745) Deprecate PropertyFileSnitch
[ https://issues.apache.org/jira/browse/CASSANDRA-10745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1511#comment-1511 ] Brandon Williams commented on CASSANDRA-10745: -- GPFS will already fall back to the property file if the node-specific dc-rack file isn't there, so you could just keep packaging it that way and use GPFS instead of PFS. > 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)
[jira] [Commented] (CASSANDRA-10745) Deprecate PropertyFileSnitch
[ https://issues.apache.org/jira/browse/CASSANDRA-10745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15062037#comment-15062037 ] Sean Durity commented on CASSANDRA-10745: - Thank you for considering my comment. I don't have any preference on the exact implementation details. Either of the options above still lets me distribute the same configuration files to every node, which is my request. I appreciate your work! > 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)
[jira] [Commented] (CASSANDRA-10745) Deprecate PropertyFileSnitch
[
https://issues.apache.org/jira/browse/CASSANDRA-10745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15061178#comment-15061178
]
Paulo Motta commented on CASSANDRA-10745:
-
Thanks for the input [~sdurity]. We could probably make the
{{PropertyFileSnitch}} use the {{GossipingPropertyFileSnitch}} internally,
fetching only the local node's information from
{{cassandra-topology.properties}} file while ignoring other node's info from
this file (which will be propagated by gossip as in GPFS).
Alternatively we could still deprecate {{PropertyFileSnitch}} while making
{{GossipingPropertyFileSnitch}} support the {{cassandra-topology.properties}}
file to allow having a single global 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)
[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)
