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

Jonathan Ellis commented on CASSANDRA-10444:
--------------------------------------------

Really a subset of CASSANDRA-8303 but I suppose we could special case it for 
old versions.

> Create an option to forcibly disable tracing
> --------------------------------------------
>
>                 Key: CASSANDRA-10444
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10444
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            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.4#6332)

Reply via email to