[
https://issues.apache.org/jira/browse/CASSANDRA-11098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15472411#comment-15472411
]
Greg Lloyd commented on CASSANDRA-11098:
----------------------------------------
I am having the same exact issue. I can't find any guidance on whats the
correct way to handle this, what did you end up doing?
> 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)
