You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2013/10/01 00:16:24 UTC

[jira] [Commented] (CASSANDRA-6016) Ability to change replication factor for the trace keyspace

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

Jonathan Ellis commented on CASSANDRA-6016:
-------------------------------------------

What happens if I have a cluster where I change RF to 2, then add a new node that says "I'd better create traces locally since it doesn't exist?"

> Ability to change replication factor for the trace keyspace
> -----------------------------------------------------------
>
>                 Key: CASSANDRA-6016
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6016
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Jeremiah Jordan
>            Assignee: Yuki Morishita
>            Priority: Minor
>             Fix For: 2.0.2
>
>         Attachments: 6016-2.0.txt, 6016-2.0-v2.txt
>
>
> They trace keyspace is currently RF=1, and can't be changed.  I want to be able to trace stuff when nodes are down/being stupid.



--
This message was sent by Atlassian JIRA
(v6.1#6144)