Return-Path: 
 <user-return-32028-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org>
X-Original-To: apmail-cassandra-user-archive@www.apache.org
Delivered-To: apmail-cassandra-user-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id A9006E086
	for <apmail-cassandra-user-archive@www.apache.org>;
 Tue, 19 Feb 2013 09:29:51 +0000 (UTC)
Received: (qmail 65582 invoked by uid 500); 19 Feb 2013 09:29:49 -0000
Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org
Received: (qmail 65356 invoked by uid 500); 19 Feb 2013 09:29:49 -0000
Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@cassandra.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@cassandra.apache.org>
List-Post: <mailto:user@cassandra.apache.org>
List-Id: <user.cassandra.apache.org>
Reply-To: user@cassandra.apache.org
Delivered-To: mailing list user@cassandra.apache.org
Received: (qmail 65336 invoked by uid 99); 19 Feb 2013 09:29:48 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Feb 2013 09:29:48 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of haithem.jarraya@struq.com
 designates 209.85.128.176 as permitted sender)
Received: from [209.85.128.176] (HELO mail-ve0-f176.google.com)
 (209.85.128.176)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Feb 2013 09:29:41 +0000
Received: by mail-ve0-f176.google.com with SMTP id cz10so5542423veb.21
        for <user@cassandra.apache.org>; Tue, 19 Feb 2013 01:29:19 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=google.com; s=20120113;
        h=mime-version:x-received:date:message-id:subject:from:to
         :content-type:x-gm-message-state;
        bh=Ugd6eLhim/2CrBRjeA/lOe91CJVlMiI+zltWg/frC1s=;
        b=dAV3FUEuxfBMi9ak4MIvXhJRcE+3VqADdoS9qWJLiO0spWFPPH/Is3OsCR1DAL0lUz
         RrbubCRFBa+eRLsrAdk4BidHcUgFSR0wViLeYvabVM3j19vTXaVPsXUaPS4+3yUVMF52
         B/Vt7q1GLqnE+DUVq8daikwLxWsPqTxLNd4jsh2EuRaIiBLDzA8bH8zL9T8LDmfcP7Jd
         Z7PX5JOh0MdEFJF5vk928HEoXh+HXKDmyoXDRtbhX4rW4xbf0gTN/OOVeYdgGzrlfMrP
         125jioa2iMjgsy+RaFYVk+JG01+8C33xyIQn0rmxI8mdW2YGQ3iDCX1zPeAO71jY3m8p
         HHBg==
MIME-Version: 1.0
X-Received: by 10.58.145.106 with SMTP id st10mr20161017veb.39.1361266159542;
 Tue, 19 Feb 2013 01:29:19 -0800 (PST)
Received: by 10.58.230.41 with HTTP; Tue, 19 Feb 2013 01:29:19 -0800 (PST)
Date: Tue, 19 Feb 2013 09:29:19 +0000
Message-ID: 
 <CAKimya1L4=t0sLz=-_e+C_bQb=9fr8R9vgWJuFk-+=YBm2MKcQ@mail.gmail.com>
Subject: Long running nodetool repair
From: Haithem Jarraya <haithem.jarraya@struq.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=047d7b5d88efe2633304d61079d3
X-Gm-Message-State: 
 ALoCoQkZ9ABzIq9SoEnJ5MuKAQMfwSPGm5ypTsCWEiFNAEkSqnmfJnX0aTz8HbdHVktrV/eVcJFJ
X-Virus-Checked: Checked by ClamAV on apache.org

--047d7b5d88efe2633304d61079d3
Content-Type: text/plain; charset=ISO-8859-1

Hi,

I am new to Cassandra and I am not sure if this is the normal behavior but
nodetool repair runs for too long even for small dataset per node. As I am
writing I started a nodetool repair last night at 18:41 and now it's 9:18
and it's still running, the size of my data is only ~500mb per node.
We have
3 Node cluster in DC1 with RF 3
1 Node Cluster in DC2 with RF 1
1 Node cluster in DC3 with RF 1

and running Cassandra V1.2.1 with 256 vNodes.

>From cassandra logs I do not see AntiEntropy logs anymore only compaction
Task and FlushWriter.

Is this a normal behaviour of nodetool repair?
Is the running time grow linearly with the size of the data?

Any help or direction will be much appreciated.


Thanks,

H

--047d7b5d88efe2633304d61079d3
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<div><br></div><div style>I am new to Cassandra and I a=
m not sure if this is the normal=A0behavior=A0but nodetool repair runs for =
too long even for small dataset per node. As I am writing I started a nodet=
ool repair last night at 18:41 and now it&#39;s 9:18 and it&#39;s still run=
ning, the size of my data is only ~500mb per node.</div>
<div style>We have</div><div style>3 Node cluster in DC1 with RF 3</div><di=
v style>1 Node Cluster in DC2 with RF 1</div><div style>1 Node cluster in D=
C3 with RF 1</div><div style><br></div><div style>and running Cassandra V1.=
2.1 with 256 vNodes.</div>
<div style><br></div><div style>From cassandra logs I do not see AntiEntrop=
y logs anymore only compaction Task and FlushWriter.</div><div style><br></=
div><div style>Is this a normal behaviour of nodetool repair?</div><div sty=
le>
Is the running time grow linearly with the size of the data?</div><div styl=
e><br></div><div style>Any help or direction will be much appreciated.</div=
><div style><br></div><div style><br></div><div style>Thanks,</div><div sty=
le>
<br></div><div style>H</div></div>

--047d7b5d88efe2633304d61079d3--