Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B6798DD7A for ; Thu, 8 Nov 2012 14:59:16 +0000 (UTC) Received: (qmail 98535 invoked by uid 500); 8 Nov 2012 14:59:15 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 98402 invoked by uid 500); 8 Nov 2012 14:59:14 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 98085 invoked by uid 99); 8 Nov 2012 14:59:14 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Nov 2012 14:59:14 +0000 Date: Thu, 8 Nov 2012 14:59:14 +0000 (UTC) From: "Jonathan Ellis (JIRA)" To: commits@cassandra.apache.org Message-ID: <585992565.86996.1352386754582.JavaMail.jiratomcat@arcas> In-Reply-To: <243682504.38137.1351492754373.JavaMail.jiratomcat@arcas> Subject: [jira] [Resolved] (CASSANDRA-4869) repair cannot complete MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-4869?page=3Dcom.atla= ssian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis resolved CASSANDRA-4869. --------------------------------------- Resolution: Invalid =20 > repair cannot complete > ---------------------- > > Key: CASSANDRA-4869 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4869 > Project: Cassandra > Issue Type: Bug > Components: Core, Documentation & website, Tools > Affects Versions: 1.1.6 > Environment: oracle java 1.6u35, oracle java 1.6u37, linux 2.6.32 > Reporter: Zenek Kraweznik > > ERROR [ValidationExecutor:3] 2012-10-24 16:41:24,310 AbstractCassandraDae= mon.java (line 135) Exception in thread Thread[ValidationExecutor:3,1,main] > java.lang.AssertionError: row DecoratedKey(738976093979458169440094759427= 93437831, 37663364336664642d353532642d343736392d613437662d37633965633962363= 7386138) received out of order wrt DecoratedKey(104298997089014216307657576= 199722210661, > 65396135326632372d343065352d343864372d616362372d326665373738616434366334) > at org.apache.cassandra.service.AntiEntropyService$Validator.add(= AntiEntropyService.java:349) > at org.apache.cassandra.db.compaction.CompactionManager.doValidat= ionCompaction(CompactionManager.java:716) > at org.apache.cassandra.db.compaction.CompactionManager.access$60= 0(CompactionManager.java:69) > at org.apache.cassandra.db.compaction.CompactionManager$8.call(Co= mpactionManager.java:442) > at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) > at java.util.concurrent.FutureTask.run(Unknown Source) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown= Source) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Sou= rce) > at java.lang.Thread.run(Unknown Source) > I've also found in log file: > ERROR [CompactionExecutor:2974] 2012-10-26 02:59:21,384 LeveledManifest.j= ava (line 223) At level 3, SSTableReader(path=3D'/var/lib/cassandra/data/Ar= chive/Messages/Archive-Messages-hf-97756-Data.db') [DecoratedKey(7208934751= 7688459378407444327185359483, 31343563626135612d323439342d346633312d6161303= 82d653133623336303032363464), DecoratedKey(10429899708901421630765757619972= 2210661, 65396135326632372d343065352d343864372d616362372d326665373738616434= 366334)] overlaps SSTableReader(path=3D'/var/lib/cassandra/data/Archive/Mes= sages/Archive-Messages-hf-97519-Data.db') [DecoratedKey(7389760939794581694= 4009475942793437831, 37663364336664642d353532642d343736392d613437662d376339= 656339623637386138), DecoratedKey(104617537605721927860229960625668693343, = 39613736316364352d313361392d343163322d383361642d623635366163623032376430)].= This is caused by a bug in Cassandra 1.1.0 .. 1.1.3. Sending back to L0.= If you have not yet run scrub, you should do so since you may also have r= ows out-of-order within an sstable > but I'd have run scrub on all nodes before repair action -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs For more information on JIRA, see: http://www.atlassian.com/software/jira