Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Message-ID: <10989638.121841288276821360.JavaMail.jira@thor>
Date: Thu, 28 Oct 2010 10:40:21 -0400 (EDT)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Subject: [jira] Commented: (CASSANDRA-1674) Repair using abnormally large
 amounts of disk space, dropping messages
In-Reply-To: <8309010.121821288276702271.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925817#action_12925817 ] 

Jonathan Ellis commented on CASSANDRA-1674:
-------------------------------------------

(this is rc1 snapshot, btw)

> Repair using abnormally large amounts of disk space, dropping messages
> ----------------------------------------------------------------------
>
>                 Key: CASSANDRA-1674
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1674
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Jonathan Ellis
>             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.