You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "DOAN DuyHai (JIRA)" <ji...@apache.org> on 2017/03/13 11:42:41 UTC
[jira] [Comment Edited] (CASSANDRA-10444) Create an option to
forcibly disable tracing
[ https://issues.apache.org/jira/browse/CASSANDRA-10444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15907292#comment-15907292 ]
DOAN DuyHai edited comment on CASSANDRA-10444 at 3/13/17 11:42 AM:
-------------------------------------------------------------------
Does _ALTER KEYSPACE system_traces WITH replication=\{ ....., 'replication_factor': 0\}_ sufficient enough for the trick ?
was (Author: doanduyhai):
Does {{ALTER KEYSPACE system_traces WITH replication=\{ ....., 'replication_factor': 0\} }} sufficient enough for the trick ?
> Create an option to forcibly disable tracing
> --------------------------------------------
>
> Key: CASSANDRA-10444
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10444
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Brandon Williams
> Priority: Minor
> Fix For: 2.1.x
>
>
> Sometimes people will experience dropped TRACE messages. Ostensibly, trace is disabled on the server and we know it's from some client, somewhere. With an inability to locate exactly where client code is causing this, it would be useful to just be able to kill it entirely on the server side.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)