Hi Alex,
I'm using Cassandra reaper as well. Could be
https://issues.apache.org/jira/browse/CASSANDRA-14332 as it was committed
in both version.
Regards,
Maxim.
On Wed, Aug 29, 2018 at 2:14 PM Oleksandr Shulgin <
oleksandr.shul...@zalando.de> wrote:
> On Wed, Aug 29, 2018 at 3:06 AM Maxim
Hi,
I wanted to get rid of https://issues.apache.org/jira/browse/CASSANDRA-14332
and https://issues.apache.org/jira/browse/CASSANDRA-14470. I haven't seen
these errors yet, but it is early to say after couple of days of operation.
Regards,
Maxim.
On Wed, Aug 29, 2018 at 10:27 AM Jean Carlo
On Wed, Aug 29, 2018 at 3:06 AM Maxim Parkachov
wrote:
> couple of days ago I have upgraded Cassandra from 3.11.2 to 3.11.3 and I
> see that repair time is practically doubled. Does someone else experience
> the same regression ?
>
We have upgraded from 3.0.16 to 3.0.17 two days ago and we see
Hello,
Can I ask you why did you upgrade from 3.11.2 ? did you experience some
java heap problems ?
Unfortunately I cannot answer your question :( I am in the 2.1 and about to
upgrade to 3.11
Best greatings
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
On Wed,
Hi everyone,
couple of days ago I have upgraded Cassandra from 3.11.2 to 3.11.3 and I
see that repair time is practically doubled. Does someone else experience
the same regression ?
Regards,
Maxim.