You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2011/03/09 20:53:59 UTC
[jira] Updated: (CASSANDRA-2301) OOM on repair with many
inconsistent ranges
[ https://issues.apache.org/jira/browse/CASSANDRA-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-2301:
--------------------------------------
Reviewer: jbellis
Description:
Repair can OOM when lots of ranges are inconsistent, causing many sstables to be streamed.
I replicated the error by making 1264 3MB sstables on one node, added a second node, changed the replication factor to 2, and ran a repair.
Looking at the heap dump of the original failure, there were 2.4GB of FutureTasks, each taking up 8MB of space. I tracked down the BufferedRandomAccessFile and made sure that it was cleared every time it was closed inside of src/java/org/apache/cassandra/io/sstable/SSTableWriter.java.
Attached is the patch I used which stopped the error when I was trying to replicate it.
was:
On repair, the java heap space tends to OOM.
I replicated the error by making 1264 3MB sstables on one node, added a second node, changed the replication factor to 2, and ran a repair.
Looking at the heap dump of the original failure, there were 2.4GB of FutureTasks, each taking up 8MB of space. I tracked down the BufferedRandomAccessFile and made sure that it was cleared every time it was closed inside of src/java/org/apache/cassandra/io/sstable/SSTableWriter.java.
Attached is the patch I used which stopped the error when I was trying to replicate it.
Affects Version/s: (was: 0.7.1)
0.7.0
Assignee: Joaquin Casares
Summary: OOM on repair with many inconsistent ranges (was: OOM on repair)
> OOM on repair with many inconsistent ranges
> -------------------------------------------
>
> Key: CASSANDRA-2301
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2301
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 0.7.0
> Reporter: Joaquin Casares
> Assignee: Joaquin Casares
> Fix For: 0.7.4
>
> Attachments: 2301.diff
>
>
> Repair can OOM when lots of ranges are inconsistent, causing many sstables to be streamed.
> I replicated the error by making 1264 3MB sstables on one node, added a second node, changed the replication factor to 2, and ran a repair.
> Looking at the heap dump of the original failure, there were 2.4GB of FutureTasks, each taking up 8MB of space. I tracked down the BufferedRandomAccessFile and made sure that it was cleared every time it was closed inside of src/java/org/apache/cassandra/io/sstable/SSTableWriter.java.
> Attached is the patch I used which stopped the error when I was trying to replicate it.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira