Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of tmarthinussen@gmail.com
 designates 74.125.82.44 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=CfBEAEVhwW5H7TftEat5leaB6cpuOeMjIDS5nZzfqO3eZWPDbtB7z6pdfSiCNLM8xQ
         3tpodnZjCBTtAtZvUUczQEWbDFSd58dNDb/+hwzDQFcU5ynEmKhvSjfAllkFY5FVVPXR
         godX7Qw1h8mv7Hr2FgZCknOoEpeabA0T9YKZw=
MIME-Version: 1.0
Date: Tue, 14 Jun 2011 16:21:14 +0900
Message-ID: <BANLkTinzi_wwfS7mOsgQ1C_Q1YXPGaym9w@mail.gmail.com>
Subject: repair and amount of transfers
From: Terje Marthinussen <tmarthinussen@gmail.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=20cf30207b2899b2d604a5a6e150

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

Hi,

I have been testing repairs a bit in different ways on 0.8.0 and I am
curious on what to really expect in terms of data transferred.

I would expect my data to be fairly consistent in this case from the start.
More than a billion supercolumns, but there was no errors in feed and we
have seen minimal amounts of read repair going on while doing a complete
scan of the data for consistency checking. As such, I would also expect
repair to finish reasonably fast.

On some nodes, it finishes in a couple of hours, but other nodes it is
taking more than 12 hours and I see some 65GB of data streamed to the node
which surprises me as I am pretty sure that it is not that out of sync.

Not sure how much the merkle trees are actually reducing what needs to be
streamed though.

What should we expect to see if this works?

Regards,
Terje

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

Hi,=A0<div><br></div><div>I have been testing repairs a bit in different wa=
ys on 0.8.0 and I am curious on what to really expect in terms of data tran=
sferred.</div><div><br></div><div>I would expect my data to be fairly consi=
stent in this case from the start. More than a billion supercolumns, but th=
ere was no errors in feed and we have seen minimal amounts of read repair g=
oing on while doing a complete scan of the data for consistency checking. A=
s such, I would also expect repair to finish reasonably fast.</div>
<div><br></div><div>On some nodes, it finishes in a couple of hours, but ot=
her nodes it is taking more than 12 hours and I see some 65GB of data strea=
med to the node which surprises me as I am pretty sure that it is not that =
out of sync.</div>
<div><br></div><div>Not sure how much the merkle trees are actually reducin=
g what needs to be streamed though.</div><div><br></div><div>What should we=
 expect to see if this works?</div><div><br></div><div>Regards,</div><div>
Terje=A0</div>

--20cf30207b2899b2d604a5a6e150--