Hi,
We have upgraded the system from Cassandra 2.1.16 to 3.11.1. After about
335M of data loading, repair with –pr and –full option was triggered for
all keyspaces (7 keyspaces). Data size of main_k1 is ~170G.
Please find the command executed for repair:
*…./cassandra/bin/nodetool -u -
> 3.11.1 is effectively three sequential patch releases, and the tick-tock
>> releases offered a number of superior fixes and performance improvements
>> over what was done in 3.0.x.
>>
>> Introduce the use of new features later on, one at a time, after thorough
>> testing and staging.
>>
>> regards,
>> Mick
>>
>
>
>
--
-Shini Gupta
""Trusting in God won't make the mountain smaller,
But will make climbing easier.
Do not ask God for a lighter load
But ask Him for a stronger back... ""
the past that working in a rush on Cassandra often
> creates more issues than solutions in general.
>
> C*heers,
> ---
> Alain Rodriguez - @arodream - al...@thelastpickle.com
> France / Spain
>
> The Last Pickle - Apache Cassandra Consulting
> http://ww
Hi
Can someone please answer this query?
Thanks
On Wed, Dec 6, 2017 at 9:58 AM, shini gupta <gupta.sh...@gmail.com> wrote:
> If we have upgraded Cassandra binaries from 2.0 to 2.1 on ALL the nodes
> but upgradesstable is still pending, please provide the impact of following
If we have upgraded Cassandra binaries from 2.0 to 2.1 on ALL the nodes but
upgradesstable is still pending, please provide the impact of following
scenarios:
1. Running nodetool repair on one of the nodes while upgradesstables is
still executing on one or more nodes in the cluster.
2. Running
Hi
Which version of Cassandra 3.x is stable and production-ready?
Regards
