[
https://issues.apache.org/jira/browse/CASSANDRA-13970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17371412#comment-17371412
]
Brandon Williams commented on CASSANDRA-13970:
----------------------------------------------
Marking this for 4.1 as I do think this should happen.
> Remove PFS compatibility mode from GPFS
> ---------------------------------------
>
> Key: CASSANDRA-13970
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13970
> Project: Cassandra
> Issue Type: Task
> Components: Local/Config
> Reporter: Paulo Motta (Deprecated)
> Assignee: Paulo Motta (Deprecated)
> Priority: Low
> Fix For: 4.1
>
>
> {{GossipingPropertyFileSnitch}} (GPFS) has a compatibility mode which
> fallbacks to {{PropertyFileSnitch}} (PFS) to fetch rack/dc info from
> {{conf/cassandra-rackdc.properties}} when a node info is not found in Gossip.
> The problem is that we supply a default {{conf/cassandra-rackdc.properties}},
> which is loaded in clusters (as shown in the log below) and may affect ring
> layout before gossip settles potentially leading to issues such
> CASSANDRA-13948.
> {code:none}
> INFO [main] 2017-10-12 14:39:32,928 GossipingPropertyFileSnitch.java:64 -
> Loaded cassandra-topology.properties for compatibility
> {code}
> I see 2 options to preven this from causing similar problems in the future:
> a) Remove PFS compatibility mode
> a) Move {{conf/cassandra-rackdc.properties}} to {{examples}} or
> {{conf/examples}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
