> > 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 looking up the file in the source code. You do have to be careful you don't disable valuable log messages this way however, as I believe you can only change the log level at the package level, which might hide some important messages. Having said that it's worth testing at the class level as I haven't actually tried that myself. For most software I'd advise against running DEBUG in production, however for Cassandra you probably still want to keep DEBUG on. Some work has been done to improve logging, but there is still a large amount of useful info exposed in the debug logs that will likely be necessary at some point in time. raft.so - Cassandra consulting, support, and managed services On Thu, Feb 18, 2021 at 2:12 AM Jai Bheemsen Rao Dhanwada < jaibheem...@gmail.com> wrote: > 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 to log only what I need instead of the > entire DEBUG logs. Also in general I am not sure if enabling DEBUG logs in > production environments is a good idea. > > On Wed, Feb 17, 2021 at 4:58 AM Paulo Motta <pauloricard...@gmail.com> > wrote: > >> > 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., 17 de fev. de 2021 às 05:52, Kane Wilson <k...@raft.so> escreveu: >> >>> 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 consulting, support, managed services >>> >>> On Wed., 17 Feb. 2021, 16:48 Erick Ramirez, <erick.rami...@datastax.com> >>> wrote: >>> >>>> 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 a cluster >>>> (but I'm sure someone has a different preference). If there's a problem, it >>>> will make it very difficult to troubleshoot and identify the cause. Most of >>>> those messages were reconfigured to DEBUG level just so it wouldn't be >>>> so noisy in the system.log. Cheers! >>>> >>>>>
