cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-8182) Comparison method violates its general contract in IndexSummaryManager.redistributeSummaries
Date Fri, 24 Oct 2014 07:46:34 GMT


Sylvain Lebresne commented on CASSANDRA-8182:

bq.  does this affect the stability of the cluster?

No. When this happen, the task that check if it can reduce the memory of index summary (as
per CASSANDRA-5519) will fail, but the whole thing is not critical in the first place (it's
more a nice to have really) and it's retried every hour anyway (and it almost certainly won't
fail consistently). Fixing this is more about removing a scary error from the log, it's largly
unconsequential in practice.

> Comparison method violates its general contract in IndexSummaryManager.redistributeSummaries
> --------------------------------------------------------------------------------------------
>                 Key: CASSANDRA-8182
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: 2.1.0
>            Reporter: Juho Mäkinen
>            Assignee: Tyler Hobbs
>             Fix For: 2.1.2
> I found this exception while going over the logs of my new 2.1.0 production candidate
> ERROR [IndexSummaryManager:1] 2014-10-23 14:37:56,727 - Exception
in thread Thread[IndexSummaryManager:1,1,main]
> java.lang.IllegalArgumentException: Comparison method violates its general contract!
>         at java.util.TimSort.mergeLo( ~[na:1.7.0_67]
>         at java.util.TimSort.mergeAt( ~[na:1.7.0_67]
>         at java.util.TimSort.mergeCollapse( ~[na:1.7.0_67]
>         at java.util.TimSort.sort( ~[na:1.7.0_67]
>         at java.util.TimSort.sort( ~[na:1.7.0_67]
>         at java.util.Arrays.sort( ~[na:1.7.0_67]
>         at java.util.Collections.sort( ~[na:1.7.0_67]
>         at
>         at
>         at$1.runMayThrow(
>         at ~[apache-cassandra-2.1.0.jar:2.1.0]
>         at org.apache.cassandra.concurrent.DebuggableScheduledThreadPoolExecutor$
>         at java.util.concurrent.Executors$ [na:1.7.0_67]
>         at java.util.concurrent.FutureTask.runAndReset( [na:1.7.0_67]
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(
>         at java.util.concurrent.ScheduledThreadPoolExecutor$
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(
>         at java.util.concurrent.ThreadPoolExecutor$
>         at [na:1.7.0_67]
> There's some other cases of invalid comparison methods in the past, but not from this

This message was sent by Atlassian JIRA

View raw message