Does enabling probabilistic tracing in Cassandra (3.11.2) stops some internal work?
When I set 0 probability back, it goes up.

Bringing together the Apache Cassandra experts from the community and DataStax.
Want to learn? Have a question? Want to share your expertise? You are in the right place!
Not sure where to begin? Getting Started
Tracing does not prevent tasks from operating but since tracing is a very expensive operation, it can significantly impact the performance of your cluster.
Depending on how busy your cluster is, exercise a lot of caution when enabling probabilistic tracing. Only enable it on one node at a time and start with a very low value, say 0.1% (probability value of 0.001
).
Monitor the performance of the node for at least 5-10 minutes. Only increase the probability in very small increments if absolutely necessary.
If you see any negative effects, disable tracing immediately. We recommend that you don't leave tracing on unless you are actively monitoring the performance of your cluster. Cheers!
5 People are following this question.
DataStax Enterprise is powered by the best distribution of Apache Cassandra ™
© 2022 DataStax, Titan, and TitanDB are registered trademarks of DataStax, Inc. and its subsidiaries in the United States and/or other countries.
Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries.
Privacy Policy Terms of Use