+1 on removing 'DEBUG' level.
I would stay at 'INFO' level, for the same reason, unless you are really
debugging something ;-).
C*heers,
---
Alain Rodriguez - @arodream - al...@thelastpickle.com
France / Spain
The Last Pickle - Apache Cassandra Consulting
http://www.thelastpi
In certain versions (2.2 specifically) I’ve seen a massive performance hit from
the extra logging in some very specific circumstances. In the case I looked at
it was due to the added overhead of reflection. The issue I found was resolved
in 3.0 (I think), but I always disable DEBUG logging now
Hi,
Do you guys enable debug log in production? Is it recommended?
By default, the cassandra log level is set to debug:
https://github.com/apache/cassandra/blob/trunk/conf/logback.xml#L100
We’re using 3.0.x, which generates lots of Gossip messages:
FailureDetector.java:456 - Ignoring interval ti
