cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-10444) Create an option to forcibly disable tracing
Date Mon, 05 Oct 2015 19:30:26 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-10444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Brandon Williams updated CASSANDRA-10444:
-----------------------------------------
         Assignee: Joshua McKenzie
    Fix Version/s: 2.1.x

> 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
>            Assignee: Joshua McKenzie
>            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)

Mime
View raw message