gmail.com>]
> *Sent:* Wednesday, January 04, 2017 12:22 AM
> *To:* user@cassandra.apache.org
> *Subject:* Re: Incremental repair for the first time
>
>
>
> Thank you!
>
>
>
> We are planning to upgrade to 3.0.10 for this issue.
>
>
>
> From the NEW
Nodetool-upgradesstables-FAQ
>
> From: Kathiresan S [mailto:kathiresanselva...@gmail.com]
> Sent: Wednesday, January 04, 2017 12:22 AM
> To: user@cassandra.apache.org
> Subject: Re: Incremental repair for the first time
>
> Thank you!
>
> We are planning to upgrade to 3.0.10 f
/hc/en-us/articles/208040036-Nodetool-upgradesstables-FAQ
From: Kathiresan S [mailto:kathiresanselva...@gmail.com]
Sent: Wednesday, January 04, 2017 12:22 AM
To: user@cassandra.apache.org
Subject: Re: Incremental repair for the first time
Thank you!
We are planning to upgrade to 3.0.10
Thank you!
We are planning to upgrade to 3.0.10 for this issue.
>From the NEWS txt file (
https://github.com/apache/cassandra/blob/trunk/NEWS.txt), it looks like
there is no need for sstableupgrade when we upgrade from 3.0.4 to 3.0.10
(i.e. Just installing 3.0.10 Cassandra would suffice and it
No workarounds, your best/only option is to upgrade (plus you get the
benefit of loads of other bug fixes).
On 16 December 2016 at 21:58, Kathiresan S
wrote:
> Thank you!
>
> Is any work around available for this version?
>
> Thanks,
> Kathir
>
>
> On Friday,
Thank you!
Is any work around available for this version?
Thanks,
Kathir
On Friday, December 16, 2016, Jake Luciani wrote:
> This was fixed post 3.0.4 please upgrade to latest 3.0 release
>
> On Fri, Dec 16, 2016 at 4:49 PM, Kathiresan S <
> kathiresanselva...@gmail.com
>
This was fixed post 3.0.4 please upgrade to latest 3.0 release
On Fri, Dec 16, 2016 at 4:49 PM, Kathiresan S
wrote:
> Hi,
>
> We have a brand new Cassandra cluster (version 3.0.4) and we set up
> nodetool repair scheduled for every day (without any options for
Hi,
We have a brand new Cassandra cluster (version 3.0.4) and we set up
nodetool repair scheduled for every day (without any options for repair).
As per documentation, incremental repair is the default in this case.
Should we do a full repair for the very first time on each node once and
then