[
https://issues.apache.org/jira/browse/CASSANDRA-13970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16212044#comment-16212044
]
Jeremiah Jordan commented on CASSANDRA-13970:
---------------------------------------------
I would suggests that we also change the order of falling back to the file and
reading from the system table. We should only fall back to comparability node
if we don’t have any information in gossip or the system tables.
> Remove PFS compatibility mode from GPFS
> ---------------------------------------
>
> Key: CASSANDRA-13970
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13970
> Project: Cassandra
> Issue Type: Task
> Components: Configuration
> Reporter: Paulo Motta
> Assignee: Paulo Motta
> Priority: Minor
>
> {{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
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
