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 B7EE2C867 for ; Thu, 7 Jun 2012 09:37:27 +0000 (UTC) Received: (qmail 74033 invoked by uid 500); 7 Jun 2012 09:37:27 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 73936 invoked by uid 500); 7 Jun 2012 09:37:26 -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 73863 invoked by uid 99); 7 Jun 2012 09:37:23 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Jun 2012 09:37:23 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 3C16414285F for ; Thu, 7 Jun 2012 09:37:23 +0000 (UTC) Date: Thu, 7 Jun 2012 09:37:23 +0000 (UTC) From: "Yanis Biziuk (JIRA)" To: commits@cassandra.apache.org Message-ID: <235309284.47080.1339061843248.JavaMail.jiratomcat@issues-vm> In-Reply-To: <1926656139.46041.1336593228131.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (CASSANDRA-4233) overlapping sstables in leveled compaction strategy MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-4233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13290906#comment-13290906 ] Yanis Biziuk commented on CASSANDRA-4233: ----------------------------------------- Stack trace of this error ERROR 04:09:21,216 Exception in thread Thread[CompactionExecutor:410,1,main] java.lang.AssertionError: Last written key DecoratedKey(144093708553026671072703572185472027831, 00000000003eef36) >= current key DecoratedKey(50602742485951681279829043048319220646, 00000000004506bf) writing into /cassandra/data/Server/Messages/Server-Messages-tmp-hd-5380-Data.db at org.apache.cassandra.io.sstable.SSTableWriter.beforeAppend(SSTableWriter.java:134) at org.apache.cassandra.io.sstable.SSTableWriter.append(SSTableWriter.java:153) at org.apache.cassandra.db.compaction.CompactionTask.execute(CompactionTask.java:159) at org.apache.cassandra.db.compaction.LeveledCompactionTask.execute(LeveledCompactionTask.java:50) at org.apache.cassandra.db.compaction.CompactionManager$1.runMayThrow(CompactionManager.java:150) at org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:30) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Linux version 2.6.32-5-amd64 (Debian 2.6.32-45) 32GB ram, 24 threads (12 cores) We are upgraded Cassandra server from repository(config file was overwritten, but we change it later). And we REcreated keyspace with all CF (we in not a production stage yet). all us CFs UPDATE COLUMN FAMILY Messages WITH compression_options={sstable_compression:SnappyCompressor, chunk_length_kb:1}; UPDATE COLUMN FAMILY Messages WITH compaction_strategy=LeveledCompactionStrategy AND compaction_strategy_options={sstable_size_in_mb: 10}; UPDATE COLUMN FAMILY Messages WITH gc_grace = 0; This CF has many inserts in one time. Over 1000-3000 keys with 9 columns each in one sec. And this CF has 4 secondary indexes (numbers ~ from 1 to 20) More info about Cassandra server partitioner: org.apache.cassandra.dht.RandomPartitioner key_cache_size_in_mb - default row_cache_size_in_mb - default row_cache_provider: SerializingCacheProvider MAX_HEAP_SIZE="8G" HEAP_NEWSIZE="2G" Thanks for any help. > overlapping sstables in leveled compaction strategy > --------------------------------------------------- > > Key: CASSANDRA-4233 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4233 > Project: Cassandra > Issue Type: Bug > Affects Versions: 1.1.0 > Reporter: Jonathan Ellis > Assignee: Sylvain Lebresne > Fix For: 1.1.1 > > Attachments: 0001-Make-sure-Leveled-compaction-always-use-the-right-min-.txt, 4233-assert.txt, 4233-v2.txt, 4233-v3.txt, 4233-v4.txt, system.log.bz2 > > > CASSANDRA-4142 introduces test failures, that are caused by overlapping tables within a level, which Shouldn't Happen. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira