Just read the source and well… yup. I’m guessing now that the options are
indeed only rolling repair on each node (with -pr stopping the duplicate work)
or -st -9223372036854775808 -et 9223372036854775807 to actually cover all
ranges. I didn’t walk through to test that, though.
Glad 3.0 is
On Mon, Apr 13, 2015 at 11:43 PM, Jeff Ferland j...@tubularlabs.com wrote:
Just read the source and well… yup. I’m guessing now that the options are
indeed only rolling repair on each node (with -pr stopping the duplicate
work) or -st -9223372036854775808 -et 9223372036854775807 to actually
What about incremental repair and sequential repair?
I ran nodetool repair -- keyspace table on one node. I found the repair
sessions running on different nodes. Will this command repair the whole
table?
In this page:
On Mon, Apr 13, 2015 at 1:36 PM, Benyi Wang bewang.t...@gmail.com wrote:
- I need to run compaction one each node,
In general, there is no requirement to manually run compaction. Minor
compaction occurs in the background, automatically.
- To repair a table (column family), I only
I read the document for several times, but I still not quite sure how to
run repair and compaction.
To my understanding,
- I need to run compaction one each node,
- To repair a table (column family), I only need to run repair on any of
nodes.
Am I right?
Thanks.
On Mon, Apr 13, 2015 at 3:33 PM, Jeff Ferland j...@tubularlabs.com wrote:
Nodetool repair -par: covers all nodes, computes merkle trees for each
node at the same time. Much higher IO load as every copy of a key range is
scanned at once. Can be totally OK with SSDs and throughput limits. Only
Or use spotify’s reaper and forget about it
https://github.com/spotify/cassandra-reaper
https://github.com/spotify/cassandra-reaper
On Apr 13, 2015, at 3:45 PM, Robert Coli rc...@eventbrite.com wrote:
On Mon, Apr 13, 2015 at 3:33 PM, Jeff Ferland j...@tubularlabs.com
