, although
some are still using nb-* sstables.
Thanks
Luciano Greiner
On Tue, Mar 18, 2025 at 12:26 PM Luciano Greiner
wrote:
>
> Amazing!
>
> So this is not a big deal having nodes running on mixed versions of
> sstables for a while.
>
> Thank you !
>
> Luciano Greiner
>
Amazing!
So this is not a big deal having nodes running on mixed versions of
sstables for a while.
Thank you !
Luciano Greiner
On Tue, Mar 18, 2025 at 12:09 PM Paul Chandler wrote:
>
> Hi Luciano,
>
> It is not a must, as, after the node is upgraded all the new sstables will be
One thing I am not really sure is if upgrading sstables is really a
must after the Cassandra 5 upgrade.
Thanks
Luciano Greiner
On Sun, Mar 16, 2025 at 2:33 PM Paul Chandler wrote:
>
> Yes, that should sort it out.
>
> Regards
>
> Paul
> Sent from my iPhone
>
>
Thank you Paul!
So should I restart the nodes with UPGRADING mode and run the
upgradesstables again?
Thank you!
Luciano Greiner
(54) 996309845
On Sun, Mar 16, 2025 at 2:58 AM Paul Chandler wrote:
>
> Hi Luciano,
>
> It sounds like you could have the storage_compatibility_mod
Hi,
We recently upgraded our clusters from 4.1.5 to 5.0.3 and now I’m
trying to migrate SSTable files to the new oa-* format, but it’s not
working as I expected.
What I Tried:
nodetool flush + upgradesstables → Completed quickly with success
messages, but no SSTables were rewritten.
nodetool upg
copy of the old file as it will
keep pointing to the old inodes.
Luciano Greiner
On Thu, Mar 13, 2025 at 11:23 PM William Crowell
wrote:
> Luciano,
>
>
>
> That is very possible. Any reasons why the increased disk space from
> version 3 to 4? Did anything in particular change
Haven't you forgot to clean some snapshots ?
Luciano Greiner
On Thu, Mar 13, 2025 at 11:18 PM William Crowell via user <
user@cassandra.apache.org> wrote:
> Hi,
>
>
>
> Is this mailing list still active?
>
>
>
> Thanks.
>
>
>
> *From: *Willi
t;
> Given this, it maybe best to split this operation, firstly to provision the
> new nodes with 4.1.3, then upgrade the nodes to Cassandra 5.
>
> Thanks
>
> Paul
>
>
>
> > On 30 Jan 2025, at 02:38, Luciano Greiner wrote:
> >
> > Hello.
> >
> &g
Hello.
I am upgrading a small Cassandra 4.1.3 cluster (2 sites, 3 nodes each)
to Cassandra 5.
Given we're using an old Centos OS in our nodes, I decided to get new
nodes provisioned in the cluster (with version 5 on compatibility
mode), and then decommission the old nodes when all is completed.
We are a about to do the same upgrade, although aiming v4.1.2
Highly interested in this topic as well.
Luciano Greiner
On Thu, Jan 11, 2024 at 4:13 AM ranju goel wrote:
>
> Hi Everyone,
>
> We are planning to upgrade from 4.0.11 to 4.1.3, the main motive of upgrading
> is 4.0.
Hello.
This company I am working for has small production cluster with the
following setup:
2 DCs
3 nodes each
RF = 3 (all keyspaces)
num_tokens = 4
repairs are up to date
We are in the process of adding more nodes to the cluster, although
while testing our procedures on a staging cluster (same
11 matches
Mail list logo
