Details
-
Improvement
-
Status: Open
-
Low
-
Resolution: Unresolved
-
None
-
None
Description
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.
Attachments
Issue Links
- relates to
-
CASSANDRA-8303 Create a capability limitation framework
- Open