You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Stu Hood (JIRA)" <ji...@apache.org> on 2010/11/15 20:10:18 UTC
[jira] Updated: (CASSANDRA-1674) Repair using abnormally large
amounts of disk space
[ https://issues.apache.org/jira/browse/CASSANDRA-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stu Hood updated CASSANDRA-1674:
--------------------------------
Summary: Repair using abnormally large amounts of disk space (was: Repair using abnormally large amounts of disk space, dropping messages)
> Repair using abnormally large amounts of disk space
> ---------------------------------------------------
>
> Key: CASSANDRA-1674
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1674
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Stu Hood
> Fix For: 0.7.1
>
>
> I'm watching a repair on a 7 node cluster. Repair was sent to one node; the node had 18G of data. No other node has more than 28G. The node where the repair initiated is now up to 261G with 53/60 AES tasks outstanding.
> I have seen repair take more space than expected on 0.6 but nothing this extreme.
> Other nodes in the cluster are occasionally logging
> WARN [ScheduledTasks:1] 2010-10-28 08:31:14,305 MessagingService.java (line 515) Dropped 7 messages in the last 1000ms
> The cluster is quiesced except for the repair. Not sure if the dropped messages are contributing the the disk space (b/c of retries?).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.