Thanks for the tip Eric. We're actually on 3.2 and the issue isn't with the
Reaper. The issue is with Cassandra. It will report that a table has
pending compactions, but it will never actually start compacting. The
pending number stays at that level until we run a manual compaction.
-richard
On
We had issues where Reaper would never actually start some repairs. The GUI
would say RUNNING but the progress would be 0/.
Datastax support said there is a bug and recommended upgrading to 3.2.
Upgrading Reaper to 3.2 resolved our issue.
Hope this helps.
Eric
From: Richard Hesse
Sent: S
Sorry about that. 4.0.6
On Sun, Oct 30, 2022, 11:19 AM Dinesh Joshi wrote:
> It would be helpful if you could tell us what version of Cassandra you’re
> using?
>
> Dinesh
>
> > On Oct 30, 2022, at 10:07 AM, Richard Hesse wrote:
> >
> >
> > Hi, I'm hoping to get some help with a vexing issue w
It would be helpful if you could tell us what version of Cassandra you’re using?
Dinesh
> On Oct 30, 2022, at 10:07 AM, Richard Hesse wrote:
>
>
> Hi, I'm hoping to get some help with a vexing issue with one of our
> keyspaces. During Reaper repair sessions, one keyspace will end up with
>
