Kurt,
I have created https://issues.apache.org/jira/browse/CASSANDRA-14709 as a
request for enhancement. Not sure if/how this gets attention though.
Thanks for your support.
Thomas
From: kurt greaves
Sent: Montag, 13. August 2018 13:30
To: User
Subject: Re: Configuration parameter to reject
Yeah I meant 2.2. Keep telling myself it was 3.0 for some reason.
On 20 August 2018 at 19:29, Oleksandr Shulgin
wrote:
> On Mon, Aug 13, 2018 at 1:31 PM kurt greaves wrote:
>
>> No flag currently exists. Probably a good idea considering the serious
>> issues with incremental repairs since forev
On Mon, Aug 13, 2018 at 1:31 PM kurt greaves wrote:
> No flag currently exists. Probably a good idea considering the serious
> issues with incremental repairs since forever, and the change of defaults
> since 3.0.
>
Hi Kurt,
Did you mean since 2.2 (when incremental became the default one)? Or
No flag currently exists. Probably a good idea considering the serious
issues with incremental repairs since forever, and the change of defaults
since 3.0.
On 7 August 2018 at 16:44, Steinmaurer, Thomas <
thomas.steinmau...@dynatrace.com> wrote:
> Hello,
>
>
>
> we are running Cassandra in AWS an
Hello,
we are running Cassandra in AWS and On-Premise at customer sites, currently 2.1
in production with 3.11 in loadtest.
In a migration path from 2.1 to 3.11.x, I'm afraid that at some point in time
we end up in incremental repairs being enabled / ran a first time
unintentionally, cause:
a)
