Hi Gil,

All the logging is controlled via logback. You can change the level of any type 
of message.

Take a look here for some more details: 
https://docs.datastax.com/en/cassandra-oss/3.0/cassandra/configuration/configLoggingLevels.html
 
<https://docs.datastax.com/en/cassandra-oss/3.0/cassandra/configuration/configLoggingLevels.html>

Thanks 

Paul Chandler
www.redshots.com

> On 10 Mar 2020, at 08:56, Gil Ganz <gilg...@gmail.com> wrote:
> 
> That's one option, I wish I there was a way to disable just that and not the 
> entire debug log level, there are some things there I would like to keep.
> 
> On Sun, Mar 8, 2020 at 6:41 PM Jeff Jirsa <jji...@gmail.com 
> <mailto:jji...@gmail.com>> wrote:
> There are likely two log configs - one for debug.log and one for system.log. 
> Disable the debug.log one, or change org.apache.cassandra.service to log at 
> INFO instead 
> 
> Nobody needs to see every digest mismatch and that someone thought this was a 
> good idea is amazing to me. Someone should jira that to be a trace.
> 
> 
>> On Mar 8, 2020, at 3:25 AM, Gil Ganz <gilg...@gmail.com 
>> <mailto:gilg...@gmail.com>> wrote:
>> 
>> 
>> Thanks Shalom, I know why these read repairs are happening, and they will 
>> continue to happen for some time, even if I will run a full repair. 
>> I would like to disable these warning messages.
>> 
>> On Sun, Mar 8, 2020 at 10:19 AM Shalom Sagges <shalomsag...@gmail.com 
>> <mailto:shalomsag...@gmail.com>> wrote:
>> Hi Gil, 
>> 
>> You can run a full repair on your cluster. But if these messages come back 
>> again, you need to check what's causing these data inconsistencies. 
>> 
>> 
>> On Sun, Mar 8, 2020 at 10:11 AM Gil Ganz <gilg...@gmail.com 
>> <mailto:gilg...@gmail.com>> wrote:
>> Hey all
>> I have a lot of debug message about read repairs in my debug log :
>> 
>> DEBUG [ReadRepairStage:346] 2020-03-08 08:09:12,959 ReadCallback.java:242 - 
>> Digest mismatch:
>> org.apache.cassandra.service.DigestMismatchException: Mismatch for key 
>> DecoratedKey(-333328476014476640, 
>> 00040000008700001130303a33613a37643a33613a62643a383000) 
>> (38d3509295a283326ffffa71887113fc vs 033cbba98c43e7ba6f15c0ba462f5fcc)
>>         at 
>> org.apache.cassandra.service.DigestResolver.compareResponses(DigestResolver.java:92)
>>  ~[apache-cassandra-3.11.5.jar:3.11.5]
>>         at 
>> org.apache.cassandra.service.ReadCallback$AsyncRepairRunner.run(ReadCallback.java:233)
>>  ~[apache-cassandra-3.11.5.jar:3.11.5]
>>         at 
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>>  [na:1.8.0_201]
>>         at 
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>>  [na:1.8.0_201]
>>         at 
>> org.apache.cassandra.concurrent.NamedThreadFactory.lambda$threadLocalDeallocator$0(NamedThreadFactory.java:84)
>>  [apache-cassandra-3.11.5.jar:3.11.5]
>>         at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_201]
>> 
>> Version is 3.11.5, anyone knows how to disable just these warnings?
>> Thanks
>> Gil
>> 

Reply via email to