cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefania (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-12014) IndexSummary > 2G causes an assertion error
Date Mon, 19 Sep 2016 09:02:20 GMT


Stefania commented on CASSANDRA-12014:

Currently running the 3.0 tests for the following patch, based on [~jjirsa] original code


The idea is to avoid hitting the assertion by estimating an average key size (by looking at
either the primary index or the index summaries of existing sstables), and to automatically
increase min_index_interval if the total estimated size of the index summary is more than

If we still hit the 2GB limit despite our best efforts to avoid this, we basically give up
on the summary for the final part of the sstable. We could re-sample on the fly by dropping
half the entries or extend the summary with multiple memory regions but I thought this would
be an overkill, and early opening complicates matters further. I think we can live with a
linear scan of the primary index if we hit 2G in the summary, as far as I understood the code
the only down-side is a linear scan of the primary index for the final part of the sstable.

> IndexSummary > 2G causes an assertion error
> -------------------------------------------
>                 Key: CASSANDRA-12014
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Brandon Williams
>            Assignee: Stefania
>            Priority: Minor
>             Fix For: 3.0.x, 3.x
> {noformat}
> ERROR [CompactionExecutor:1546280] 2016-06-01 13:21:00,444
- Exception in thread Thread[CompactionExecutor:1546280,1,main]
> java.lang.AssertionError: null
>     at
>     at$IndexWriter.append(
>     at
>     at ~[cassandra-all-]
>     at
>     at org.apache.cassandra.db.compaction.CompactionTask.runMayThrow(
>     at ~[cassandra-all-]
>     at org.apache.cassandra.db.compaction.CompactionTask.executeInternal(
>     at org.apache.cassandra.db.compaction.AbstractCompactionTask.execute(
>     at org.apache.cassandra.db.compaction.CompactionManager$
>     at java.util.concurrent.Executors$ ~[na:1.7.0_51]
>     at ~[na:1.7.0_51]
>     at java.util.concurrent.ThreadPoolExecutor.runWorker(
>     at java.util.concurrent.ThreadPoolExecutor$
>     at [na:1.7.0_51]
> {noformat}
> I believe this can be fixed by raising the min_index_interval, but we should have a better
method of coping with this than throwing the AE.

This message was sent by Atlassian JIRA

View raw message