[CASSANDRA-1066] DatacenterShardStrategy needs enforceable and keyspace based RF

• Type: Improvement
• Status: Resolved
• Priority: Low
• Resolution: Fixed
• Fix Version/s: 0.7 beta 1
• Assignee: Jeremy Hanna
• Reporter: Jeremy Hanna

Authors

Jeremy Hanna

• Created: 07/May/10 20:50
• Updated: 16/Apr/19 09:33
• Resolved: 31/Jul/10 15:43

Description

(Updated to reflect the true scope of this improvement along with decisions about implementation)

Currently, the DatacenterShardStrategy reads in a properties file - datacenters.properties - to get a per-datacenter replication factor.

This improvement would do away with a separate properties file for configuring per-datacenter replication in favor of configuring them on a per-keyspace basis. This would allow clients to create a new keyspace with the configuration of the DatacenterShardStrategy as part of the keyspace definition. It would also update the cassandra.yaml configuration parsing to allow users to configure their DSS from there as well.

The basic structure would not change and the KSMetaData would just contain additional configuration information - a map of configuration options. That way, if other ReplicationStrategies in the future would like specific configuration options, they can use them as well.

Further changes previously mentioned in this ticket involved enforcing the replication factor. A separate ticket has been created to push the replication factor down to the replication strategy. That facilitates enforcing the RF at that level.

Issue Links

• is depended upon by: CASSANDRA-1263 Push replication factor down to the replication strategy
• relates to: CASSANDRA-1344 Update CLI add keyspace usage to take into account replication strategy options