Marc/Dimitry/Jon - greatly appreciate your feedback. I will look into the
version part that you suggested. The reason to go direct to 3.x is to take
a bi leap and reduce overall effort to upgrade a large cluster (development
included).
I have these questions from my original post. Appreciate if yo
On Fri, 30 Nov 2018, 17:54 Oliver Herrmann When using nodetool refresh I must have write access to the data folder
> and I have to do it on every node. In our production environment the user
> that would do the restore does not have write access to the data folder.
>
OK, not entirely sure that's
Dmitry is right. Generally speaking always go with the latest bug fix
release.
On Sat, Dec 1, 2018 at 10:14 AM Dmitry Saprykin
wrote:
> See more here
> https://issues.apache.org/jira/plugins/servlet/mobile#issue/CASSANDRA-13004
>
> On Sat, Dec 1, 2018 at 1:02 PM Dmitry Saprykin
> wrote:
>
>> Ev
See more here
https://issues.apache.org/jira/plugins/servlet/mobile#issue/CASSANDRA-13004
On Sat, Dec 1, 2018 at 1:02 PM Dmitry Saprykin
wrote:
> Even more, 3.0.9 is a terrible target choice by itself. It has a nasty bug
> corrupting sstables on alter.
>
> On Sat, Dec 1, 2018 at 11:55 AM Marc Se
Even more, 3.0.9 is a terrible target choice by itself. It has a nasty bug
corrupting sstables on alter.
On Sat, Dec 1, 2018 at 11:55 AM Marc Selwan
wrote:
> Hi Shravan,
>
> Did you upgrade Apache Cassandra 2.1.9 to the latest patch release before
> doing the major upgrade? It's generally favora
Hi Shravan,
Did you upgrade Apache Cassandra 2.1.9 to the latest patch release before
doing the major upgrade? It's generally favorable to go to the latest patch
release as often times they include fixes that smooth over the upgrade
process. There are hundreds of bug fixes between 2.1.9 and 2.1.20
