Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Message-ID: <3036231.3161273521511112.JavaMail.jira@thor>
Date: Mon, 10 May 2010 15:58:31 -0400 (EDT)
From: "Jeremy Hanna (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Subject: [jira] Assigned: (CASSANDRA-1066) DatacenterShardStrategy needs
 enforceable and keyspace based RF
In-Reply-To: <6655713.39891273265507708.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jeremy Hanna reassigned CASSANDRA-1066:
---------------------------------------

    Assignee: Jeremy Hanna

> DatacenterShardStrategy needs enforceable and keyspace based RF
> ---------------------------------------------------------------
>
>                 Key: CASSANDRA-1066
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1066
>             Project: Cassandra
>          Issue Type: Improvement
>    Affects Versions: 0.7
>            Reporter: Jeremy Hanna
>            Assignee: Jeremy Hanna
>            Priority: Minor
>
> Currently, the DatacenterShardStrategy reads in a properties file - datacenters.properties - to get a per-datacenter replication factor.  So any keyspace that is using the DSS in the cluster is using that same properties file to configure its replication factor.  The implementation doesn't take into account the per-keyspace replication factor, but it is assumed that the sum of all the datacenter RF values equals the per-keyspace replication value that is part of the keyspace metadata.
> It seems that an improvement could be two-fold:
> 1. Enforce the replication factor for the keyspace as always equal the sum of all the datacenter RF values.  Otherwise, if they aren't equal, bad things (tm) can happen.
> 2. Make the datacenter RF values part of the keyspace metadata rather than a global value.  Again, currently if any keyspace in the cluster is configured to use DSS, it will be using the global DC RF values found in the properties file.  An improvement could be to instead of having the properties file, configure that on a per keyspace basis.  That would make the cluster more multi-tenant friendly so it could be flexible with multiple keyspaces.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.