> 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! >> >>>
