completed. So, I push to get upgradesstables completed as soon as possible.
Sean Durity
From: Shravan R
Sent: Tuesday, December 04, 2018 3:39 PM
To: user@cassandra.apache.org
Subject: Re: [EXTERNAL] Re: upgrade Apache Cassandra 2.1.9 to 3.0.9
Thanks Sean. I have automation in place that can put
ember 04, 2018 12:22 PM
> *To:* user@cassandra.apache.org
> *Subject:* [EXTERNAL] Re: upgrade Apache Cassandra 2.1.9 to 3.0.9
>
>
>
> Thanks Jeff. I tried to bootstrap a 3.x node to a partially upgraded
> cluster (2.1.9 + 3.x) and I was *not* able to do so. The schema never
&
Schema won’t be transferred cross-majors
--
Jeff Jirsa
> On Dec 4, 2018, at 10:51 PM, Shravan R wrote:
>
> Thanks Jeff. I tried to bootstrap a 3.x node to a partially upgraded cluster
> (2.1.9 + 3.x) and I was not able to do so. The schema never settled.
>
> How does the below approach so
quickly necessary (security issue or bug
fix).
Sean Durity
From: Shravan R
Sent: Tuesday, December 04, 2018 12:22 PM
To: user@cassandra.apache.org
Subject: [EXTERNAL] Re: upgrade Apache Cassandra 2.1.9 to 3.0.9
Thanks Jeff. I tried to bootstrap a 3.x node to a partially upgraded cluster
(2.1.9
Thanks Jeff. I tried to bootstrap a 3.x node to a partially upgraded
cluster (2.1.9 + 3.x) and I was *not* able to do so. The schema never
settled.
How does the below approach sound like?
1. Update the software binary on all nodes to use cassandra-3.x upon a
restart.
2. Restart all nodes
> On Dec 2, 2018, at 12:40 PM, Shravan R wrote:
>
> 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)
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
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
Hello,
I am planning to upgrade Apache Cassandra 2.1.9 to Apache Cassandra-3.0.9.
I came up with the version based on [1]. I followed upgrade steps as in
[2]. I was testing the same in the lab and encountered issues (streaming
just fails and hangs for ever) with bootstrapping a 3.0.9 node on a
par
12 matches
Mail list logo
