[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-tabpanelfocusedCommentId=13826900#comment-13826900 ] Jackson Chung commented on CASSANDRA-6016: -- will there be a further 1.2(.12) release? if so, can this be put in 1.2 please? thx 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-v2.txt, 6016-2.0-v3.txt, 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 was sent by Atlassian JIRA (v6.1#6144)
[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-tabpanelfocusedCommentId=13826942#comment-13826942 ] Jonathan Ellis commented on CASSANDRA-6016: --- This is more of a new feature than a bug fix, so no. 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-v2.txt, 6016-2.0-v3.txt, 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 was sent by Atlassian JIRA (v6.1#6144)
[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-tabpanelfocusedCommentId=13783573#comment-13783573 ] Jonathan Ellis commented on CASSANDRA-6016: --- +1 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, 6016-2.0-v3.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)
[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-tabpanelfocusedCommentId=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)
[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-tabpanelfocusedCommentId=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()
{
ListCFMetaData 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
