cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wei Deng (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-11098) system_distributed keyspace uses a hard-coded replication factor
Date Sat, 30 Jan 2016 01:01:48 GMT

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

Wei Deng commented on CASSANDRA-11098:
--------------------------------------

on the same token, system_traces keyspace has a similar problem. See this code:

https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/tracing/TraceKeyspace.java#L78

> system_distributed keyspace uses a hard-coded replication factor
> ----------------------------------------------------------------
>
>                 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 the save 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