as
>
>
>
> *From:* kurt greaves [mailto:k...@instaclustr.com]
> *Sent:* Montag, 15. Jänner 2018 06:18
> *To:* User
> *Subject:* Re: Cleanup blocking snapshots - Options?
>
>
>
> Disabling the snapshots is the best and only real option other than
> upgrading at the mom
ent: Montag, 15. Jänner 2018 06:18
To: User
Subject: Re: Cleanup blocking snapshots - Options?
Disabling the snapshots is the best and only real option other than upgrading
at the moment. Although apparently it was thought that there was only a small
race condition in 2.1 that triggered this and
om]
> *Sent:* Montag, 15. Jänner 2018 06:18
> *To:* User
> *Subject:* Re: Cleanup blocking snapshots - Options?
>
>
>
> Disabling the snapshots is the best and only real option other than
> upgrading at the moment. Although apparently it was thought that there was
> only a sm
to re-evaluate this situation ☺
Regards,
Thomas
From: kurt greaves [mailto:k...@instaclustr.com]
Sent: Montag, 15. Jänner 2018 06:18
To: User
Subject: Re: Cleanup blocking snapshots - Options?
Disabling the snapshots is the best and only real option other than upgrading
at the moment. Although
Disabling the snapshots is the best and only real option other than
upgrading at the moment. Although apparently it was thought that there was
only a small race condition in 2.1 that triggered this and it wasn't worth
fixing. If you are triggering it easily maybe it is worth fixing in 2.1 as
well.
Hello,
we are running 2.1.18 with vnodes in production and due to
(https://issues.apache.org/jira/browse/CASSANDRA-11155) we can't run cleanup
e.g. after extending the cluster without blocking our hourly snapshots.
What options do we have to get rid of partitions a node does not own anymore?
*
