[jira] [Commented] (CASSANDRA-14900) DigestMismatchException log messages should be at TRACE
[ https://issues.apache.org/jira/browse/CASSANDRA-14900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17380674#comment-17380674 ] Brandon Williams commented on CASSANDRA-14900: -- Committed, thank you! > DigestMismatchException log messages should be at TRACE > --- > > Key: CASSANDRA-14900 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14900 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Observability, Local/Config >Reporter: Aleksandr Sorokoumov >Assignee: Aleksandr Sorokoumov >Priority: Low > Fix For: 3.0.25, 3.11.11 > > > DigestMismatchException log messages should probably be at TRACE. These log > messages about normal digest mismatches that include scary stacktraces: > {noformat} > DEBUG [ReadRepairStage:40] 2017-10-24 19:45:50,349 ReadCallback.java:242 - > Digest mismatch: > org.apache.cassandra.service.DigestMismatchException: Mismatch for key > DecoratedKey(-786225366477494582, > 31302e33322e37382e31332d6765744469736b5574696c50657263656e742d736463) > (943070f62d72259e3c25be0c6f76e489 vs f4c7c7675c803e0028992e11e0bbc5a0) > at > org.apache.cassandra.service.DigestResolver.compareResponses(DigestResolver.java:92) > ~[cassandra-all-3.11.0.1855.jar:3.11.0.1855] > at > org.apache.cassandra.service.ReadCallback$AsyncRepairRunner.run(ReadCallback.java:233) > ~[cassandra-all-3.11.0.1855.jar:3.11.0.1855] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > [na:1.8.0_121] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > [na:1.8.0_121] > at > org.apache.cassandra.concurrent.NamedThreadFactory.lambda$threadLocalDeallocator$0(NamedThreadFactory.java:81) > [cassandra-all-3.11.0.1855.jar:3.11.0.1855] > at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_121] > {noformat} -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14900) DigestMismatchException log messages should be at TRACE
[ https://issues.apache.org/jira/browse/CASSANDRA-14900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17380647#comment-17380647 ] Brandon Williams commented on CASSANDRA-14900: -- +1 > DigestMismatchException log messages should be at TRACE > --- > > Key: CASSANDRA-14900 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14900 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Observability, Local/Config >Reporter: Aleksandr Sorokoumov >Assignee: Aleksandr Sorokoumov >Priority: Low > Fix For: 3.0.x, 3.11.x > > > DigestMismatchException log messages should probably be at TRACE. These log > messages about normal digest mismatches that include scary stacktraces: > {noformat} > DEBUG [ReadRepairStage:40] 2017-10-24 19:45:50,349 ReadCallback.java:242 - > Digest mismatch: > org.apache.cassandra.service.DigestMismatchException: Mismatch for key > DecoratedKey(-786225366477494582, > 31302e33322e37382e31332d6765744469736b5574696c50657263656e742d736463) > (943070f62d72259e3c25be0c6f76e489 vs f4c7c7675c803e0028992e11e0bbc5a0) > at > org.apache.cassandra.service.DigestResolver.compareResponses(DigestResolver.java:92) > ~[cassandra-all-3.11.0.1855.jar:3.11.0.1855] > at > org.apache.cassandra.service.ReadCallback$AsyncRepairRunner.run(ReadCallback.java:233) > ~[cassandra-all-3.11.0.1855.jar:3.11.0.1855] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > [na:1.8.0_121] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > [na:1.8.0_121] > at > org.apache.cassandra.concurrent.NamedThreadFactory.lambda$threadLocalDeallocator$0(NamedThreadFactory.java:81) > [cassandra-all-3.11.0.1855.jar:3.11.0.1855] > at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_121] > {noformat} -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14900) DigestMismatchException log messages should be at TRACE
[ https://issues.apache.org/jira/browse/CASSANDRA-14900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17376865#comment-17376865 ] Ekaterina Dimitrova commented on CASSANDRA-14900: - I personally don't see a reason why this can be agreed in 4.0 but not good for 3.11 or 3.0. Anyway, we need one more committer reviewer or maybe [~ifesdjeen] will have some time to look at it again. > DigestMismatchException log messages should be at TRACE > --- > > Key: CASSANDRA-14900 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14900 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Observability, Local/Config >Reporter: Aleksandr Sorokoumov >Assignee: Aleksandr Sorokoumov >Priority: Low > Fix For: 3.0.x, 3.11.x > > > DigestMismatchException log messages should probably be at TRACE. These log > messages about normal digest mismatches that include scary stacktraces: > {noformat} > DEBUG [ReadRepairStage:40] 2017-10-24 19:45:50,349 ReadCallback.java:242 - > Digest mismatch: > org.apache.cassandra.service.DigestMismatchException: Mismatch for key > DecoratedKey(-786225366477494582, > 31302e33322e37382e31332d6765744469736b5574696c50657263656e742d736463) > (943070f62d72259e3c25be0c6f76e489 vs f4c7c7675c803e0028992e11e0bbc5a0) > at > org.apache.cassandra.service.DigestResolver.compareResponses(DigestResolver.java:92) > ~[cassandra-all-3.11.0.1855.jar:3.11.0.1855] > at > org.apache.cassandra.service.ReadCallback$AsyncRepairRunner.run(ReadCallback.java:233) > ~[cassandra-all-3.11.0.1855.jar:3.11.0.1855] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > [na:1.8.0_121] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > [na:1.8.0_121] > at > org.apache.cassandra.concurrent.NamedThreadFactory.lambda$threadLocalDeallocator$0(NamedThreadFactory.java:81) > [cassandra-all-3.11.0.1855.jar:3.11.0.1855] > at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_121] > {noformat} -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14900) DigestMismatchException log messages should be at TRACE
[ https://issues.apache.org/jira/browse/CASSANDRA-14900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17210846#comment-17210846 ] Aleksandr Sorokoumov commented on CASSANDRA-14900: -- Thanks for bringing it up [~e.dimitrova] ! I think the patch in its current shape is ready if we agree that it is a good idea not to print digest mismatch exceptions in debug log. > DigestMismatchException log messages should be at TRACE > --- > > Key: CASSANDRA-14900 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14900 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Observability, Local/Config >Reporter: Aleksandr Sorokoumov >Assignee: Aleksandr Sorokoumov >Priority: Low > Fix For: 3.0.x, 3.11.x > > > DigestMismatchException log messages should probably be at TRACE. These log > messages about normal digest mismatches that include scary stacktraces: > {noformat} > DEBUG [ReadRepairStage:40] 2017-10-24 19:45:50,349 ReadCallback.java:242 - > Digest mismatch: > org.apache.cassandra.service.DigestMismatchException: Mismatch for key > DecoratedKey(-786225366477494582, > 31302e33322e37382e31332d6765744469736b5574696c50657263656e742d736463) > (943070f62d72259e3c25be0c6f76e489 vs f4c7c7675c803e0028992e11e0bbc5a0) > at > org.apache.cassandra.service.DigestResolver.compareResponses(DigestResolver.java:92) > ~[cassandra-all-3.11.0.1855.jar:3.11.0.1855] > at > org.apache.cassandra.service.ReadCallback$AsyncRepairRunner.run(ReadCallback.java:233) > ~[cassandra-all-3.11.0.1855.jar:3.11.0.1855] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > [na:1.8.0_121] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > [na:1.8.0_121] > at > org.apache.cassandra.concurrent.NamedThreadFactory.lambda$threadLocalDeallocator$0(NamedThreadFactory.java:81) > [cassandra-all-3.11.0.1855.jar:3.11.0.1855] > at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_121] > {noformat} -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14900) DigestMismatchException log messages should be at TRACE
[ https://issues.apache.org/jira/browse/CASSANDRA-14900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17210296#comment-17210296 ] Ekaterina Dimitrova commented on CASSANDRA-14900: - Hi [~Ge] and [~ifesdjeen], Any thoughts about this ticket? I haven't looked at the patch but it looks like you both agreed on it? > DigestMismatchException log messages should be at TRACE > --- > > Key: CASSANDRA-14900 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14900 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Observability, Local/Config >Reporter: Aleksandr Sorokoumov >Assignee: Aleksandr Sorokoumov >Priority: Low > Fix For: 3.0.x, 3.11.x > > > DigestMismatchException log messages should probably be at TRACE. These log > messages about normal digest mismatches that include scary stacktraces: > {noformat} > DEBUG [ReadRepairStage:40] 2017-10-24 19:45:50,349 ReadCallback.java:242 - > Digest mismatch: > org.apache.cassandra.service.DigestMismatchException: Mismatch for key > DecoratedKey(-786225366477494582, > 31302e33322e37382e31332d6765744469736b5574696c50657263656e742d736463) > (943070f62d72259e3c25be0c6f76e489 vs f4c7c7675c803e0028992e11e0bbc5a0) > at > org.apache.cassandra.service.DigestResolver.compareResponses(DigestResolver.java:92) > ~[cassandra-all-3.11.0.1855.jar:3.11.0.1855] > at > org.apache.cassandra.service.ReadCallback$AsyncRepairRunner.run(ReadCallback.java:233) > ~[cassandra-all-3.11.0.1855.jar:3.11.0.1855] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > [na:1.8.0_121] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > [na:1.8.0_121] > at > org.apache.cassandra.concurrent.NamedThreadFactory.lambda$threadLocalDeallocator$0(NamedThreadFactory.java:81) > [cassandra-all-3.11.0.1855.jar:3.11.0.1855] > at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_121] > {noformat} -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14900) DigestMismatchException log messages should be at TRACE
[ https://issues.apache.org/jira/browse/CASSANDRA-14900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17045662#comment-17045662 ] Aleksandr Sorokoumov commented on CASSANDRA-14900: -- You are right! {{logger.trace}} was redundant there as {{traceState.trace}} was invoked right before it. I updated the patch, it only removes debug stack trace statement now. > DigestMismatchException log messages should be at TRACE > --- > > Key: CASSANDRA-14900 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14900 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Observability, Local/Config >Reporter: Aleksandr Sorokoumov >Assignee: Aleksandr Sorokoumov >Priority: Low > Fix For: 3.0.x, 3.11.x > > > DigestMismatchException log messages should probably be at TRACE. These log > messages about normal digest mismatches that include scary stacktraces: > {noformat} > DEBUG [ReadRepairStage:40] 2017-10-24 19:45:50,349 ReadCallback.java:242 - > Digest mismatch: > org.apache.cassandra.service.DigestMismatchException: Mismatch for key > DecoratedKey(-786225366477494582, > 31302e33322e37382e31332d6765744469736b5574696c50657263656e742d736463) > (943070f62d72259e3c25be0c6f76e489 vs f4c7c7675c803e0028992e11e0bbc5a0) > at > org.apache.cassandra.service.DigestResolver.compareResponses(DigestResolver.java:92) > ~[cassandra-all-3.11.0.1855.jar:3.11.0.1855] > at > org.apache.cassandra.service.ReadCallback$AsyncRepairRunner.run(ReadCallback.java:233) > ~[cassandra-all-3.11.0.1855.jar:3.11.0.1855] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > [na:1.8.0_121] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > [na:1.8.0_121] > at > org.apache.cassandra.concurrent.NamedThreadFactory.lambda$threadLocalDeallocator$0(NamedThreadFactory.java:81) > [cassandra-all-3.11.0.1855.jar:3.11.0.1855] > at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_121] > {noformat} -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14900) DigestMismatchException log messages should be at TRACE
[ https://issues.apache.org/jira/browse/CASSANDRA-14900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16727961#comment-16727961 ] Alex Petrov commented on CASSANDRA-14900: - In 4.0 we do not use exceptions for control-flow in this case anymore, and I do agree it's a good idea to avoid logging a stack trace here. But we do a [slightly different thing there|https://github.com/apache/cassandra/blob/e645b9172c5d50fc2af407de724e46121edfe109/src/java/org/apache/cassandra/service/reads/AbstractReadExecutor.java#L390], can you explain motivation for not keeping it the same across versions, since [we do have tracing in 3.0|https://github.com/Ge/cassandra/blob/14900-3.0/src/java/org/apache/cassandra/tracing/Tracing.java]? > DigestMismatchException log messages should be at TRACE > --- > > Key: CASSANDRA-14900 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14900 > Project: Cassandra > Issue Type: Bug > Components: Configuration, Observability >Reporter: Aleksandr Sorokoumov >Assignee: Aleksandr Sorokoumov >Priority: Minor > Fix For: 3.0.x, 3.11.x > > > DigestMismatchException log messages should probably be at TRACE. These log > messages about normal digest mismatches that include scary stacktraces: > {noformat} > DEBUG [ReadRepairStage:40] 2017-10-24 19:45:50,349 ReadCallback.java:242 - > Digest mismatch: > org.apache.cassandra.service.DigestMismatchException: Mismatch for key > DecoratedKey(-786225366477494582, > 31302e33322e37382e31332d6765744469736b5574696c50657263656e742d736463) > (943070f62d72259e3c25be0c6f76e489 vs f4c7c7675c803e0028992e11e0bbc5a0) > at > org.apache.cassandra.service.DigestResolver.compareResponses(DigestResolver.java:92) > ~[cassandra-all-3.11.0.1855.jar:3.11.0.1855] > at > org.apache.cassandra.service.ReadCallback$AsyncRepairRunner.run(ReadCallback.java:233) > ~[cassandra-all-3.11.0.1855.jar:3.11.0.1855] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > [na:1.8.0_121] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > [na:1.8.0_121] > at > org.apache.cassandra.concurrent.NamedThreadFactory.lambda$threadLocalDeallocator$0(NamedThreadFactory.java:81) > [cassandra-all-3.11.0.1855.jar:3.11.0.1855] > at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_121] > {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org