You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Jay Zhuang <ja...@yahoo.com.INVALID> on 2018/01/16 19:01:12 UTC

Is it recommended to enable debug log in production

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 time of 2001193771 for /IP

Probably we should back port https://github.com/apache/cassandra/commit/9ac01baef5c8f689e96307da9b29314bc0672462
Other than that, do you guys see any other issue?

Thanks,
Jay
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
For additional commands, e-mail: user-help@cassandra.apache.org


Re: Is it recommended to enable debug log in production

Posted by Alain RODRIGUEZ <ar...@gmail.com>.
+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 - alain@thelastpickle.com
France / Spain

The Last Pickle - Apache Cassandra Consulting
http://www.thelastpickle.com

2018-01-16 19:22 GMT+00:00 Jon Haddad <jo...@jonhaddad.com>:

> 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
> anyways, just in case.
>
> > On Jan 16, 2018, at 11:01 AM, Jay Zhuang <ja...@yahoo.com.INVALID>
> wrote:
> >
> > 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 time of 2001193771 for /IP
> >
> > Probably we should back port https://github.com/apache/cassandra/commit/
> 9ac01baef5c8f689e96307da9b29314bc0672462
> > Other than that, do you guys see any other issue?
> >
> > Thanks,
> > Jay
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
> > For additional commands, e-mail: user-help@cassandra.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
> For additional commands, e-mail: user-help@cassandra.apache.org
>
>

Re: Is it recommended to enable debug log in production

Posted by Jon Haddad <jo...@jonhaddad.com>.
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 anyways, just in case. 

> On Jan 16, 2018, at 11:01 AM, Jay Zhuang <ja...@yahoo.com.INVALID> wrote:
> 
> 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 time of 2001193771 for /IP
> 
> Probably we should back port https://github.com/apache/cassandra/commit/9ac01baef5c8f689e96307da9b29314bc0672462
> Other than that, do you guys see any other issue?
> 
> Thanks,
> Jay
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
> For additional commands, e-mail: user-help@cassandra.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
For additional commands, e-mail: user-help@cassandra.apache.org