r than that. It takes more time, but I separate out the admin tasks so
>>>> that I can reason what should happen. I would either scale up or upgrade
>>>> (depending on which is more urgent), then do the other.
>>>>
>>>>
>>>>
>>>>
>&
son what should happen. I would either scale up or upgrade
>>> (depending on which is more urgent), then do the other.
>>>
>>>
>>>
>>>
>>>
>>> Sean Durity
>>>
>>>
>>>
>>> *From:* manish khandelwal
>&
hat. It takes more time, but I separate out the admin tasks so
>> that I can reason what should happen. I would either scale up or upgrade
>> (depending on which is more urgent), then do the other.
>>
>>
>>
>>
>>
>> Sean Durity
>>
>>
>>
@cassandra.apache.org
Subject: [EXTERNAL] Re: Cassandra upgrade from 3.11.3 -> 3.11.6
Thank you all for the suggestions.
I am not trying to scale up the cluster for capacity but for the upgrade
process instead of in place upgrade I am planning to add nodes with 3.11.6 and
then decommission
ache.org
> *Subject:* [EXTERNAL] Re: Cassandra upgrade from 3.11.3 -> 3.11.6
>
>
>
> Rightly said by Surbhi, it is not good to scale with mixed versions as
> debugging issues will be very difficult.
>
> Better to upgrade first and then scale.
>
>
>
> Regards
that I can reason what
should happen. I would either scale up or upgrade (depending on which is more
urgent), then do the other.
Sean Durity
From: manish khandelwal
Sent: Wednesday, June 24, 2020 5:52 AM
To: user@cassandra.apache.org
Subject: [EXTERNAL] Re: Cassandra upgrade from 3.11.3 -> 3.1
>
> Can I add new nodes with the 3.11.6 version to the cluster running with
> 3.11.3?
>
Technically you can. You'll be able to add 3.11.6 nodes to a 3.11.3
cluster. In fact, the reverse works too in my tests but I personally
wouldn't want to do it in production.
> Also, I see the SSTable format
Rightly said by Surbhi, it is not good to scale with mixed versions as
debugging issues will be very difficult.
Better to upgrade first and then scale.
Regards
On Wed, Jun 24, 2020 at 11:20 AM Surbhi Gupta
wrote:
> In case of any issue, it gets very difficult to debug when we have
> multiple ve
In case of any issue, it gets very difficult to debug when we have multiple
versions.
On Tue, 23 Jun 2020 at 22:23, Jürgen Albersdorfer
wrote:
> Hi, I would say „It depends“ - as it always does. I have had a 21 Node
> Cluster running in Production in one DC with versions ranging from 3.11.1
> to
Hi, I would say „It depends“ - as it always does. I have had a 21 Node Cluster
running in Production in one DC with versions ranging from 3.11.1 to 3.11.6
without having had any single issue for over a year. I just upgraded all nodes
to 3.11.6 for the sake of consistency.
Von meinem iPhone gese
Hi ,
We have recently upgraded from 3.11.0 to 3.11.5 . There is a sstable format
change from 3.11.4 .
We also had to expand the cluster and we also discussed about expansion
first and than upgrade. But finally we upgraded and than expanded.
As per our experience what I could tell you is, it is not
Hello,
I am trying to upgrade from 3.11.3 to 3.11.6.
Can I add new nodes with the 3.11.6 version to the cluster running with
3.11.3?
Also, I see the SSTable format changed from mc-* to md-*, does this cause
any issues?
12 matches
Mail list logo