Re: 4.0 upgrade

[manish khandelwal]

Yes repairs are prohibited in mixed version cluster. If you want to monitor
please disable repairs till complete upgrade is finished

On Sat, Jul 8, 2023, 01:21 Runtian Liu  wrote:

> Hi,
>
> We are upgrading our Cassandra clusters from 3.0.27 to 4.0.6 and we
> observed some error related to repair:  j.l.IllegalArgumentException:
> Unknown verb id 32
>
> We have two datacenters for each Cassandra cluster and when we are doing
> an upgrade, we want to upgrade 1 datacenter first and monitor the upgrade
> datacenter for some time (1 week) to make sure there is no issue, then we
> will upgrade the second datacenter for that cluster.
>
> We have some automated repair jobs running, is it expected to have repair
> stuck if we have 1 datacenter on 4.0 and 1 datacenter on 3.0?
>
> Do you have any suggestions on how we should do the upgrade, is waiting
> for 1 week between two datacenters too long?
>
> Thanks,
> Runtian
>
>

Upgrade from 3.11.5 to 4.1.x

[Surbhi Gupta]

Hi,

We have to upgrade from 3.11.5 to 4.1.x .
Can we do it in one go ?
Or do we have to go to an intermediate version first?

Thanks
Surbhi

4.0 upgrade

[Runtian Liu]

Hi,

We are upgrading our Cassandra clusters from 3.0.27 to 4.0.6 and we
observed some error related to repair:  j.l.IllegalArgumentException:
Unknown verb id 32

We have two datacenters for each Cassandra cluster and when we are doing an
upgrade, we want to upgrade 1 datacenter first and monitor the upgrade
datacenter for some time (1 week) to make sure there is no issue, then we
will upgrade the second datacenter for that cluster.

We have some automated repair jobs running, is it expected to have repair
stuck if we have 1 datacenter on 4.0 and 1 datacenter on 3.0?

Do you have any suggestions on how we should do the upgrade, is waiting for
1 week between two datacenters too long?

Thanks,
Runtian