recommended upgrading to 3.2.
>
> Upgrading Reaper to 3.2 resolved our issue.
>
>
>
> Hope this helps.
>
> Eric
>
>
>
>
>
>
>
> *From:* Richard Hesse
> *Sent:* Sunday, October 30, 2022 12:07 PM
> *To:* user@cassandra.apache.org
> *Subject:* Help
: Sunday, October 30, 2022 12:07 PM
To: user@cassandra.apache.org
Subject: Help determining pending compactions
[WARNING - EXTERNAL EMAIL] Do not open links or attachments unless you
recognize the sender of this email. If you are unsure please click the button
"Report suspicious email"
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
>
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
hanging, non-started compactions. That is, the number of compactions as
reported by nodetool compactionstats stays flat and there are no running
compactions. I
