Re: best practice for repair

2017-11-13 Thread Jon Haddad 
We (The Last Pickle) maintain Reaper, an open source repair tool, specifically 
to address all the complexity around repairs.

http://cassandra-reaper.io/ <http://cassandra-reaper.io/>

Jon

> On Nov 13, 2017, at 3:18 AM, Peng Xiao <2535...@qq.com> wrote:
> 
> sub-range repair is much like primary range repair, except that each 
> sub-range repair operation focuses even smaller subset of data.
> 
> repair is a tough process.any advise?
> 
> Thanks
> 
> -- Original --
> From:  "我自己的邮箱";<2535...@qq.com>;
> Date:  Mon, Nov 13, 2017 06:51 PM
> To:  "user"<user@cassandra.apache.org>;
> Subject:  best practice for repair
> 
> Hi there,
> 
> we need to repair a huge CF,just want to clarify
> 1.nodetool repair -pr keyspace cf
> 2.nodetool repair -st -et -dc
> which will be better? or any other advice?
> 
> Thanks,
> Peng Xiao
>

Re: best practice for repair

2017-11-13 Thread Peng Xiao 
sub-range repair is much like primary range repair, except that each sub-range 
repair operation focuses even smaller subset of data.


repair is a tough process.any advise?


Thanks


-- Original --
From:  "";<2535...@qq.com>;
Date:  Mon, Nov 13, 2017 06:51 PM
To:  "user"<user@cassandra.apache.org>;

Subject:  best practice for repair



Hi there,

we need to repair a huge CF,just want to clarify
1.nodetool repair -pr keyspace cf 
2.nodetool repair -st -et -dc 
which will be better? or any other advice?


Thanks,
Peng Xiao

best practice for repair

2017-11-13 Thread Peng Xiao 
Hi there,

we need to repair a huge CF,just want to clarify
1.nodetool repair -pr keyspace cf 
2.nodetool repair -st -et -dc 
which will be better? or any other advice?


Thanks,
Peng Xiao