Hi all,
Earlier this year, we upgraded our fleet from C* 3.0 to C* 4.0. Given the
exciting new features in C* 4.1, we are contemplating an upgrade from C*
4.0 to C* 4.1. Can anyone share their experience regarding the stability of
C* 4.1? Are any of you running C* 4.1 at scale?
Additionally, I ha
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 t
cool, thank you. This looks like a very good setup for us and cleanup
should be very fast for this case.
On Tue, May 16, 2023 at 5:53 AM Jeff Jirsa wrote:
>
> In-line
>
> On May 15, 2023, at 5:26 PM, Runtian Liu wrote:
>
>
> Hi Jeff,
>
> I tried
data on the rest of the cluster. Do you know if there are any edge
cases that in this replacement process can generate any stale data on other
nodes of the cluster with the setup I mentioned?
Thanks,
Runtian
On Mon, May 8, 2023 at 9:59 PM Runtian Liu wrote:
> I thought the joining node would
token +1 (as an
> expansion), then decom the leaving node (shrink). That'll minimize
> streaming when you decommission that node.
>
>
>
> On Mon, May 8, 2023 at 7:19 PM Runtian Liu wrote:
>
>> Hi all,
>>
>> Sometimes we want to replace a node for various reas
Hi all,
Sometimes we want to replace a node for various reasons, we can replace a
node by shutting down the old node and letting the new node stream data
from other replicas, but this approach may have availability issues or data
consistency issues if one more node in the same cluster went down. W
at 7:25 PM guo Maxwell wrote:
>>
>>> compact ion will just merge duplicate data and remove delete data in
>>> this node .if you add or remove one node for the cluster, I think clean up
>>> is needed. if clean up failed, I think we should come to see the reason.
>>
Hi all,
Is cleanup the sole method to remove data that does not belong to a
specific node? In a cluster, where nodes are added or decommissioned from
time to time, failure to run cleanup may lead to data resurrection issues,
as deleted data may remain on the node that lost ownership of certain
par
Hi,
I am running Cassandra version 3.0.14 at scale on thousands of nodes. I am
planning to do a minor version upgrade from 3.0.14 to 3.0.26 in a safe
manner. My eventual goal is to upgrade from 3.0.26 to a major release 4.0.
As you know, there are multiple minor releases between 3.0.14 and 3.0.26
