On Mon, 16 Jan 2023 at 14:38, Lapo Luchini wrote:
> is upgrading Cassandra 3.11.14 → 4.1 supported,
>
3.11.14 → 4.1 is supported.
It is recommended to go to the last patch version (i.e. 3.11.14) before the
major upgrade.
Make sure to ensure all sstables are upgraded to the current format b
How do I get off this listserv?
From: Gil Ganz [mailto:gilg...@gmail.com]
Sent: Monday, July 13, 2020 11:30 AM
To: user@cassandra.apache.org
Subject: Re: Upgrading cassandra cluster from 2.1 to 3.X when using custom TWCS
Jon, great advice, I ended up doing just that, if anyone else needs
Jon, great advice, I ended up doing just that, if anyone else needs to do
the same thing, here is a 3.11.6 version
https://github.com/gilganz/twcs/tree/cassandra-3.11
Indeed switching between twcs strategies did not trigger any sstable change.
Jeff, nothing to be sorry about, gave me an opportun
On Thu, Jul 9, 2020 at 9:02 AM Oleksandr Shulgin <
oleksandr.shul...@zalando.de> wrote:
> On Thu, Jul 9, 2020 at 5:54 PM Gil Ganz wrote:
>
> Another question, did changing the compaction strategy from one twcs to
>> the other trigger merging of old sstables?
>>
>
> I don't recall any unexpected a
You could also pull TWCS out of the version of Cassandra you want to
deploy, fix the imports and change the package name. Then you've got the
same version as OSS, just under the name you're using in 2.1. Once you've
moved to 3.11, you can switch to the OSS version.
On Thu, Jul 9, 2020 at 9:09 AM
Great, thank you very much!
On Thu, Jul 9, 2020 at 7:02 PM Oleksandr Shulgin <
oleksandr.shul...@zalando.de> wrote:
> On Thu, Jul 9, 2020 at 5:54 PM Gil Ganz wrote:
>
>> That sounds very interesting Alex, so just to be sure I understand, it
>> was like this
>> 1 - you had 2.1 cluster running wit
On Thu, Jul 9, 2020 at 5:54 PM Gil Ganz wrote:
> That sounds very interesting Alex, so just to be sure I understand, it was
> like this
> 1 - you had 2.1 cluster running with the 2.1 version jar
> 2 - you upgraded to 3.0, starting the cluster with the 3.0 version jar
> that has the same strategy
That sounds very interesting Alex, so just to be sure I understand, it was
like this
1 - you had 2.1 cluster running with the 2.1 version jar
2 - you upgraded to 3.0, starting the cluster with the 3.0 version jar that
has the same strategy name
3 - you changed the compaction strategy to use the bui
On Thu, Jul 9, 2020 at 3:38 PM Gil Ganz wrote:
> Hey
> I have a 2.11.4 cluster with tables that are defined with twcs, using
> jeff's jar
>
> https://github.com/jeffjirsa/twcs
>
> All working great, but now I want to upgrade to 3.11, and I have a
> problem, cassandra won't start, it fails on the
The 3.0 branch is slightly different than the 3.11 branch
For you, going to 3.0.18 would be a minor version upgrade while going to 3.11.4
would be a major version upgrade
3.11 would give you access to features like CDC, SASI and performance
improvements like better large partition support and t
On Thu, Apr 10, 2014 at 3:52 PM, Tyler Hobbs wrote:
>
> Given the complexity of it and the multiple places this could give you
> trouble if you're not careful, I wouldn't suggest it as a general best
> practice.
>
+1. Any plan that contains an extended period of split major version
operation is
On Thu, Apr 10, 2014 at 4:03 PM, Alain RODRIGUEZ wrote:
> Would you guys consider this way of upgrading as a "best practice" to
> achieve a safe major release upgrade in the cloud (where you can easily add
> clusters and remove old ones) ?
Given the complexity of it and the multiple places this
Thanks for this confirmation Tyler.
Would you guys consider this way of upgrading as a "best practice" to
achieve a safe major release upgrade in the cloud (where you can easily add
clusters and remove old ones) ?
I am seriously thinking about giving it a try for our upcoming 1.2 to 2.0
migration
On Tue, Apr 8, 2014 at 4:39 AM, Alain RODRIGUEZ wrote:
>
> Yet, can't we rebuild a new DC with the current C* version, upgrade it to
> the new major once it is fully part of the C* cluster, and then switch all
> the clients to the new DC once we are sure everything is ok and shut down
> the old o
Hi, thanks for this information Rob.
Yet, can't we rebuild a new DC with the current C* version, upgrade it to
the new major once it is fully part of the C* cluster, and then switch all
the clients to the new DC once we are sure everything is ok and shut down
the old one ?
I mean, on a multiDC se
On Thu, Apr 3, 2014 at 8:56 AM, Alain RODRIGUEZ wrote:
> Since we use AWS EC2 instances, Is it possible to upgrade Cassandra
> through a new DC as it is recommended while switching to vnodes ?
>
No, because bootstrapping (and rebuilding/repairing/etc.) on a
split-major-version cluster is not su
You can't just drop in Apache Cassandra over DSE since it adds custom
replication strategies like this one.
On Thu, Nov 21, 2013 at 9:38 AM, Santosh Shet
wrote:
> Hi,
>
>
>
> We are facing problem while upgrading Cassandra which is available in the
> DSE 3.2 from version 1.2.11 to 2.0 .
>
> Below
On Fri, Oct 18, 2013 at 3:27 PM, Arindam Barua wrote:
> Is step 1 just to reduce downtime for the node?
>
Yes.
> Also, I’m assuming the initial_token of the new node should be set to be
> the same as the token of the old node, or close to that. Eg. [1] in
> “Replacing a Dead Node” talks about
hen.
Thanks,
Arindam
[1] http://www.datastax.com/docs/1.0/operations/cluster_management
From: Robert Coli [mailto:rc...@eventbrite.com]
Sent: Friday, October 18, 2013 11:50 AM
To: user@cassandra.apache.org
Subject: Re: upgrading Cassandra server hardware best practice?
On Fri, Oct 18, 2013 a
On Fri, Oct 18, 2013 at 11:39 AM, Arindam Barua wrote:
> ** **
>
> We currently have 2 datacenters and a ring of 5 Cassandra servers on each
> datacenter. We are getting new hardware, and after evaluating them, plan to
> upgrade the ring to the new hardware.
>
> ** **
>
> Is there any recomm
Read NEWS.txt.
0.7.6 is better than 0.7.5, btw.
On Thu, Jun 16, 2011 at 5:03 AM, Ali Ahsan wrote:
> Hi All,
>
> We are upgrading cassandra from 0.6.3 to 0.7.5.We have two node in cluster.I
> am bit confused how to upgrade them can you have any guide.
>
> --
> S.Ali Ahsan
>
> Senior System Engine
21 matches
Mail list logo
