[
https://issues.apache.org/jira/browse/CASSANDRA-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12868694#action_12868694
]
Jeremy Hanna commented on CASSANDRA-1066:
-----------------------------------------
Because of the work with CASSANDRA-952, the values in datacenters.properties
are now keyspace specific. So it solves that part of this issue. It's still a
global collection of properties, but now it has to be specified per keyspace.
So now this improvement is about 1) enforcing the RF that is originally set on
the keyspace to include what is set in datacenters.properties and 2) making
that information dynamic so that it can be updated at run time.
> DatacenterShardStrategy needs enforceable and keyspace based RF
> ---------------------------------------------------------------
>
> Key: CASSANDRA-1066
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1066
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Jeremy Hanna
> Assignee: Jeremy Hanna
> Priority: Minor
> Fix For: 0.7
>
>
> 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.
