Return-Path: 
 <user-return-25943-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 20AACC810
	for <apmail-cassandra-user-archive@www.apache.org>;
 Fri,  4 May 2012 17:31:06 +0000 (UTC)
Received: (qmail 9039 invoked by uid 500); 4 May 2012 17:31:03 -0000
Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org
Received: (qmail 9024 invoked by uid 500); 4 May 2012 17:31:03 -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 9015 invoked by uid 99); 4 May 2012 17:31:03 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 May 2012 17:31:03 +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 (nike.apache.org: domain of bill.w.au@gmail.com designates
 209.85.214.172 as permitted sender)
Received: from [209.85.214.172] (HELO mail-ob0-f172.google.com)
 (209.85.214.172)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 May 2012 17:30:56 +0000
Received: by obbeh20 with SMTP id eh20so5052036obb.31
        for <user@cassandra.apache.org>; Fri, 04 May 2012 10:30:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=BKxJt/jKZmjE+ECnSxax9sYEWUc6xomDBPy17+ylnsI=;
        b=HJ2Ms9CJzZYg/Me7MfOfStUVbommISKzt5PprIpXP2rO3otdRw4dwDAXMY8gcDGcwm
         7XyV0LeJUlYQSgb2HEYn1lNfBRWWm02GhJ2vuLFD+jib4qOfWsg81vy/tBNZlgJbFu+Y
         A4pfXYaA6j3SBmkxHulgMcQoxIVtbbLqHRonfUT20g2q+IdQ1+Qm93c6VVIJg6/nxGvu
         tqF2pKHVL/kDYYCKYKrTm0f4H0nt7rjTV+/A51QgbuzS9fk9MXJhEakwOuiP/zhbDpYq
         xxH/Vp3lOebHUJFmsuW5qV4ZLWtLOZk36KG2J1Dh8zfEYfbHnrlm+G3pjy67F+RfTMJo
         FWQw==
MIME-Version: 1.0
Received: by 10.60.22.70 with SMTP id b6mr1791099oef.5.1336152635383; Fri, 04
 May 2012 10:30:35 -0700 (PDT)
Received: by 10.182.45.7 with HTTP; Fri, 4 May 2012 10:30:35 -0700 (PDT)
Date: Fri, 4 May 2012 13:30:35 -0400
Message-ID: 
 <CAGJmZPxrf1rOcPJrY4OrE_ZDZe_9+-L6i2pCCtKxAkhv9svpSQ@mail.gmail.com>
Subject: getting status of long running repair
From: Bill Au <bill.w.au@gmail.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=e89a8fb2061632a21604bf394709

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

I know repair may take a long time to run.  I am running repair on a node
with about 15 GB of data and it is taking more than 24 hours.  Is that
normal?  Is there any way to get status of the repair?  tpstats does show 2
active and 2 pending AntiEntropySessions.  But netstats and compactionstats
show no activity.

Bill

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

I know repair may take a long time to run.=A0 I am running repair on a node=
 with about 15 GB of data and it is taking more than 24 hours.=A0 Is that n=
ormal?=A0 Is there any way to get status of the repair?=A0 tpstats does sho=
w 2 active and 2 pending AntiEntropySessions.=A0 But netstats and compactio=
nstats show no activity.<br>
<br>Bill<br>

--e89a8fb2061632a21604bf394709--