Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 27 Jun 2016 15:10:52 +0000 (UTC)
From: "Aleksey Yeschenko (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12956271.1459887132000.5559.1467040252882@Atlassian.JIRA>
In-Reply-To: <JIRA.12956271.1459887132000@Atlassian.JIRA>
References: <JIRA.12956271.1459887132000@Atlassian.JIRA> <JIRA.12956271.1459887132472@arcas>
Subject: [jira] [Updated] (CASSANDRA-11508) GPFS property file should more
 clearly explain the relationship with PFS
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 27 Jun 2016 15:10:54 -0000


     [ https://issues.apache.org/jira/browse/CASSANDRA-11508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aleksey Yeschenko updated CASSANDRA-11508:
------------------------------------------
    Fix Version/s:     (was: 2.1.15)
                   2.1.x

> GPFS property file should more clearly explain the relationship with PFS
> ------------------------------------------------------------------------
>
>                 Key: CASSANDRA-11508
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11508
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Configuration
>            Reporter: Brandon Williams
>            Priority: Trivial
>             Fix For: 2.1.x
>
>
> We should clearly explain that GPFS will load, and possibly use, the cassandra-topology.properties file if it is present.  If this is a new cluster, they should delete the topology file so that GPFS never even instantiates PFS. The topology file should only exist if they are migrating from PFS to GPFS, and be removed after the migration is complete.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)