cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6016) Ability to change replication factor for the trace keyspace
Date Fri, 27 Sep 2013 22:48:03 GMT

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

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

Does that actually work?  I would think this would be a problem:

{code}
    public static KSMetaData traceKeyspace()
    {
        List<CFMetaData> cfDefs = Arrays.asList(CFMetaData.TraceSessionsCf, CFMetaData.TraceEventsCf);
        return new KSMetaData(Tracing.TRACE_KS, SimpleStrategy.class, ImmutableMap.of("replication_factor",
"1"), true, cfDefs);
    }
{code}

Nit: I think you want case-insensitive compare on the allowAlter set.
                
> 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
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message