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
Hi all,
is upgrading Cassandra 3.11.14 → 4.1 supported, or is it better to
follow the 3.11.14 → 4.0 → 4.1 path?
(I think it is okay as i found no record of deprecated old SSTable
formats, but I couldn't manage to find any official documentation
regarding upgrade paths… forgive me
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
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
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
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
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
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
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 following error
ERROR [main] 2020-07-09 13:30:29,823
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
Hi,
we have a cluster with cassandra 3.0.9 and we are going to upgrade it to
the latest version which i think is 3.11.3 but a teamate told me that the
latest version is 3.0.17.
what is the latest stable version?
thanks in advance.
i have a cluster that is running 1.2.6. I'd like to upgrade that cluster to
2.0.7
Any suggestions/tips that would make the upgrade process smooth?
I've written a bit about upgrading from 1.1 to 1.2, non-vnodes:
http://monkeys.chaordic.com.br/operation/zero-downtime-cassandra-upgrade/
Some tips may be valid for a more recent upgrade, but I'm sure the
community has more specific tips regarding the upgrade from 1.2 to 2.0.
On Tue, May 27,
On Tue, May 27, 2014 at 10:57 AM, Eric Plowe eric.pl...@gmail.com wrote:
i have a cluster that is running 1.2.6. I'd like to upgrade that cluster
to 2.0.7
Any suggestions/tips that would make the upgrade process smooth?
As indicated in NOTES.txt, upgrades to 2.0.x must pass through at least
I'd review the CHANGES.txt to see what has changed and the NEWS.txt to see
what you need to do before upgrading (config changes, data storage changes,
etc).
Generally:
- Determine what version you are upgrading to, and why
- Snapshot the data across all nodes
- Upgrade the nodes one at a time
On Tue, May 27, 2014 at 1:24 PM, Robert Coli rc...@eventbrite.com wrote:
On Tue, May 27, 2014 at 10:57 AM, Eric Plowe eric.pl...@gmail.com wrote:
i have a cluster that is running 1.2.6. I'd like to upgrade that cluster
to 2.0.7
Any suggestions/tips that would make the upgrade process
Thanks guys!
Yea I am going to do this on a test environment that simulates our
production environment. I was just looking for any potential gotchas, etc.
On Tue, May 27, 2014 at 6:42 PM, Robert Coli rc...@eventbrite.com wrote:
On Tue, May 27, 2014 at 1:24 PM, Robert Coli
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 Thu, Apr 10, 2014 at 4:03 PM, Alain RODRIGUEZ arodr...@gmail.com 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
On Thu, Apr 10, 2014 at 3:52 PM, Tyler Hobbs ty...@datastax.com 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
On Tue, Apr 8, 2014 at 4:39 AM, Alain RODRIGUEZ arodr...@gmail.com 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
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
Hi
As we are using Cassandra 1.2.11 and we will want to move to 2.1 as soon as
it will be released and considered stable enough, we will have to make a
few migrations :
1.2.11 -- 1.2.last (16 currently)
1.2.last -- 2.0.last
2.0.last -- 2.1.last
The point is we ran into a lot of migrations
On Thu, Apr 3, 2014 at 8:56 AM, Alain RODRIGUEZ arodr...@gmail.comwrote:
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
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 is the error log we are getting while starting Cassandra.
java.lang.RuntimeException:
org.apache.cassandra.exceptions.ConfigurationException: Unable to find
replication
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
santosh.s...@vista-one-solutions.com wrote:
Hi,
We are facing problem while upgrading Cassandra which is available in the
DSE 3.2 from
On Fri, Oct 18, 2013 at 3:27 PM, Arindam Barua aba...@247-inc.com 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
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 recommended procedure for doing so? This is one of the options we
are considering:
1.
On Fri, Oct 18, 2013 at 11:39 AM, Arindam Barua aba...@247-inc.com 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
://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 at 11:39 AM, Arindam Barua
aba
Hi All,
We followed the upgrade guide(
http://www.datastax.com/docs/1.2/install/upgrading) from Datastax web site
and upgraded Cassadra to 1.2.5, but it occurred errors in system.log when
starting up.
After digging into code level, it looks like Cassandra found the file
length of IndexSummary
On Wed, May 29, 2013 at 12:32 AM, Colin Kuo colinkuo...@gmail.com wrote:
We followed the upgrade
guide(http://www.datastax.com/docs/1.2/install/upgrading) from Datastax web
site and upgraded Cassadra to 1.2.5, but it occurred errors in system.log
when starting up.
In general you should not
On 09/13/2011 05:21 PM, Jonathan Ellis wrote:
More or less. NEWS.txt explains upgrade procedure in more detail.
When moving from 0.7.x to 0.8.5 do I need to scrub all sstables post
upgrade?
NEWS.txt doesn't mention anything about that but your comment here seems
to indicate so:
Added to NEWS:
- After upgrading, run nodetool scrub against each node before running
repair, moving nodes, or adding new ones.
2011/9/14 Jonas Borgström jonas.borgst...@trioptima.com:
On 09/13/2011 05:21 PM, Jonathan Ellis wrote:
More or less. NEWS.txt explains upgrade procedure
Hi,
I am in the process of upgrading Cassandra to the recently released v0.8.5
and facing an issue.
We had two Cassandra environments - one having 0.7.0 and another 0.7.2. The
upgrade on 0.7.2 has happened smoothly, but on the environment having 0.7.0,
when I make the switch, the DB fails
Just remove the row cache files.
On Tue, Sep 13, 2011 at 8:23 AM, Roshan Dawrani roshandawr...@gmail.com wrote:
Hi,
I am in the process of upgrading Cassandra to the recently released v0.8.5
and facing an issue.
We had two Cassandra environments - one having 0.7.0 and another 0.7.2
remove the row cache files.
On Tue, Sep 13, 2011 at 8:23 AM, Roshan Dawrani roshandawr...@gmail.com
wrote:
Hi,
I am in the process of upgrading Cassandra to the recently released
v0.8.5
and facing an issue.
We had two Cassandra environments - one having 0.7.0 and another 0.7.2.
The
upgrade
)
The *KeyCache files can be removed safely in between, right?
Cheers.
On Tue, Sep 13, 2011 at 7:03 PM, Jonathan Ellis jbel...@gmail.com wrote:
Just remove the row cache files.
On Tue, Sep 13, 2011 at 8:23 AM, Roshan Dawrani roshandawr...@gmail.com
wrote:
Hi,
I am in the process of upgrading
On Tue, Sep 13, 2011 at 7:03 PM, Jonathan Ellis jbel...@gmail.com wrote:
Just remove the row cache files.
Thanks a lot. The 0.8.5 Cassandra started just fine after getting rid of
those *KeyCache files.
--
Roshan
Blog: http://roshandawrani.wordpress.com/
Twitter: @roshandawrani
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 Engineer
e-Business (Pvt) Ltd
49-C Jail Road, Lahore, P.O. Box 676
Lahore 54000, Pakistan
Tel: +92 (0)42 3758 7140
Read NEWS.txt.
0.7.6 is better than 0.7.5, btw.
On Thu, Jun 16, 2011 at 5:03 AM, Ali Ahsan ali.ah...@panasiangroup.com 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
43 matches
Mail list logo
