cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jay Zhuang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-11098) system_distributed and system_traces keyspaces use hard-coded replication factors
Date Tue, 20 Dec 2016 01:40:58 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-11098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15762899#comment-15762899
] 

Jay Zhuang commented on CASSANDRA-11098:
----------------------------------------

How about making it configurable in {{cassandra.yaml}}? So when the user change the default
snitch from {{SimpleSnitch}} to DC awarable one, she could change ToplogyStrategy for distributed
system keyspaces and add the DC information.
Not the ideal solution, but at least give the user option to configure that. Better than running
"ALTER" command while creating new clusters.

> system_distributed and system_traces keyspaces use hard-coded replication factors
> ---------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-11098
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11098
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Wei Deng
>            Priority: Minor
>
> We introduced system_distributed keyspace in C* 2.2 so that we can save the repair histories
and ancestors to a system keyspace (due to CASSANDRA-5839). However, looks like it's hard-coding
the replication factor to 3, according to this line:
> https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/repair/SystemDistributedKeyspace.java#L103
> This may confuse some query operations against this keyspace.



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

Mime
View raw message