Re: Understanding logging in Cassandra

> > Is there a list of logger names available for each task like compaction, > memtable flush etc? The logger name for a specific message is usually present in the log statement, although you may only see the file/class name (e.g StorageService.java) - in this case you can look up the package by

Re: Understanding logging in Cassandra

Thank you all, Kane: Is there a list of logger names available for each task like compaction, memtable flush etc? Paulo: I have a cluster with a very high number of tables, yes just during the boot-up time, I see a very huge number of logs in the range > 100Mb. So I am trying to tune the logging t

Re: Understanding logging in Cassandra

> I don't want to enable DEBUG logs as there are a lot of DiskBoundary messages, which are very high in volume. These messages shouldn't be very high volume as they only appear when there are ring updates, schema changes or node startup. If this is not the case please file a JIRA issue. Em qua.,

Re: Understanding logging in Cassandra

You can configure the log level of a specific package through logback, so you can silence any noisy packages by setting their level higher than debug. See http://logback.qos.ch/manual/configuration.html?source=post_page---#rootElement Cheers, Kane raft.so - Cassandra con

Re: Understanding logging in Cassandra

You can configure which log levels get logged but you can't change the log level of the log entries. For example if an entry is logged at DEBUG level, you cannot reconfigure it to be logged at INFO since the levels are defined in the code. Also, I wouldn't disable debug logging if I were managing

Understanding logging in Cassandra

Hello, I recently moved from C* version 2.1.16 to 3.11.6 and I see a lot of difference in logging between these two versions. Can someone please help me with the below questions? - Default log level in 2.1.16 is INFO