We are running 2.1.x and are currently looking into changing from STCS to
LCS, as well as enabling incremental repairs.
In what order should we do that? Should we enable incremental repairs
first, let it run its course which would mark a lot of tables as repaired,
and those marks would then carry
Ah Marcus, that looks very promising- unfortunately we have already
switched back to full repairs and our test cluster has been re-purposed for
other tasks atm. I will be sure to apply the patch/try a fixed version of
Cassandra if we attempt to migrate to incremental repair again.
Bryan, this should be improved with
https://issues.apache.org/jira/browse/CASSANDRA-10768 - could you try it
out?
On Tue, Dec 1, 2015 at 10:58 PM, Bryan Cheng wrote:
> Sorry if I misunderstood, but are you asking about the LCS case?
>
> Based on our experience, I would absolutely recommend you c
Sorry if I misunderstood, but are you asking about the LCS case?
Based on our experience, I would absolutely recommend you continue with the
migration procedure. Even if the compaction strategy is the same, the
process of anticompaction is incredibly painful. We observed our test
cluster running 2
Yes, it should now be safe to just run a repair with -inc -par to migrate
to incremental repairs
BUT, if you currently use for example repair service in OpsCenter or
Spotifys Cassandra reaper, you might still want to migrate the way it is
documented as you will have to run a full repair to migrate
Hi folks,
A question like this was recently asked, but I don't think anyone ever
supplied an unambiguous answer. We have a set of clusters currently
using sequential repair, and we'd like to transition them to
incremental repair. According to the documentation, this is a very
manual (and lik
