[prev in list] [next in list] [prev in thread] [next in thread]
List: cassandra-user
Subject: Re: Need help with incremental repair
From: Blake Eggleston <beggleston () apple ! com>
Date: 2017-10-30 20:57:53
Message-ID: etPan.59f79251.3de4d111.6b2 () apple ! com
[Download RAW message or body]
Ah cool, I didn't realize reaper did that.
On October 30, 2017 at 1:29:26 PM, Paulo Motta (pauloricardomg@gmail.com) wrote:
> This is also the case for full repairs, if I'm not mistaken. Assuming I'm not \
> missing something here, that should mean that he shouldn't need to mark sstables as \
> unrepaired?
That's right, but he mentioned that he is using reaper which uses
subrange repair if I'm not mistaken, which doesn't do anti-compaction.
So in that case he should probably mark data as unrepaired when no
longer using incremental repair.
2017-10-31 3:52 GMT+11:00 Blake Eggleston <beggleston@apple.com>:
> > Once you run incremental repair, your data is permanently marked as
> > repaired
>
> This is also the case for full repairs, if I'm not mistaken. I'll admit I'm
> not as familiar with the quirks of repair in 2.2, but prior to
> 4.0/CASSANDRA-9143, any global repair ends with an anticompaction that marks
> sstables as repaired. Looking at the RepairRunnable class, this does seem to
> be the case. Assuming I'm not missing something here, that should mean that
> he shouldn't need to mark sstables as unrepaired?
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
For additional commands, e-mail: user-help@cassandra.apache.org
[Attachment #3 (text/html)]
<html><head><style>body{font-family:Helvetica,Arial;font-size:12px}</style></head><body \
style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: \
after-white-space;"><div id="bloop_customfont" \
style="font-family:Helvetica,Arial;font-size:12px; color: rgba(0,0,0,1.0); margin: \
0px; line-height: auto;">Ah cool, I didn't realize reaper did that.</div> <div \
id="bloop_sign_1509397035961250048" class="bloop_sign"></div> <br><p \
class="airmail_on">On October 30, 2017 at 1:29:26 PM, Paulo Motta (<a \
href="mailto:pauloricardomg@gmail.com">pauloricardomg@gmail.com</a>) wrote:</p> \
<blockquote type="cite" class="clean_bq"><span><div><div></div><div>> This is also \
the case for full repairs, if I'm not mistaken. Assuming I'm not missing something \
here, that should mean that he shouldn't need to mark sstables as unrepaired? <br>
<br>That's right, but he mentioned that he is using reaper which uses
<br>subrange repair if I'm not mistaken, which doesn't do anti-compaction.
<br>So in that case he should probably mark data as unrepaired when no
<br>longer using incremental repair.
<br>
<br>2017-10-31 3:52 GMT+11:00 Blake Eggleston <beggleston@apple.com>:
<br>>> Once you run incremental repair, your data is permanently marked as
<br>>> repaired
<br>>
<br>> This is also the case for full repairs, if I'm not mistaken. I'll admit I'm
<br>> not as familiar with the quirks of repair in 2.2, but prior to
<br>> 4.0/CASSANDRA-9143, any global repair ends with an anticompaction that marks
<br>> sstables as repaired. Looking at the RepairRunnable class, this does seem to
<br>> be the case. Assuming I'm not missing something here, that should mean that
<br>> he shouldn't need to mark sstables as unrepaired?
<br>
<br>---------------------------------------------------------------------
<br>To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
<br>For additional commands, e-mail: user-help@cassandra.apache.org
<br>
<br></div></div></span></blockquote></body></html>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic