Re: [DISCUSS] Deprecate and remove resumable bootstrap and decommission

I should also add that because we use vnodes and STCS, in the absent of CASSANDRA-10540 , I don't think we will benefit from the zero copy streaming at all, as almost all SSTables files from the streaming source will contain a very wide

Re: [DISCUSS] Deprecate and remove resumable bootstrap and decommission

That was Cassandra 3.11, before the introduction of zero copy. But I must say I'm not certain whether the new zero copy streaming can prevent the long GC pauses, as I haven't tried it. On 03/08/2022 23:37, Josh McKenzie wrote: I had to resume the bootstrap once or twice in order to get these

Re: [DISCUSS] Deprecate and remove resumable bootstrap and decommission

> I had to resume the bootstrap once or twice in order to get these nodes > finish joinning the cluster. Was this before or after the addition of zero copy streaming? The premise is that the pain point resumable bootstrap targets is mitigated by the much faster bootstrapping times without the

Re: [DISCUSS] Deprecate and remove resumable bootstrap and decommission

That would have to be assessed on a case by case basis. * When the code doesn't delete data, which means there's a zero probability of resurrecting deleted data, I will still use resumable bootstrap. * When resurrected data doesn't pose a problem to the system, it often can still be an

Re: [DISCUSS] Deprecate and remove resumable bootstrap and decommission

The hypothetical concern described is around potential data resurrection - would you still use resumable bootstrap if you knew that data deleted during those STW pauses was improperly resurrected? On Wed, Aug 3, 2022 at 2:40 PM Bowen Song via dev wrote: > I have benefited from the resumable

Re: [DISCUSS] Deprecate and remove resumable bootstrap and decommission

I have benefited from the resumable bootstrap before, and I'm in favour of keeping the feature around. I've had streaming failures due to long STW GC pauses on some bootstrapping nodes, and I had to resume the bootstrap once or twice in order to get these nodes finish joinning the cluster.

[ANNOUNCEMENT] Apache Cassandra project has been accepted to participate in the GHC 2022 Open Source Day

Dear all, On behalf of the community I would like to announce that the Apache Cassandra project has been accepted to participate in the Grace Hopper Conference 2022 Open Source Day. Thank you Paulo for submitting an application! This event is a virtual hackathon-like event where participants of

Re: Cassandra project status update 2022-08-03

Re: 17738 - the ticket was about any new properties which are actually not of the new types. It had to guarantee that there is no disconnect between updating Settings Virtual Table after startup and JMX setters/getters. (In one of its “brother” tickets the issues we found exist since 4.0) I bring

[DISCUSS] Deprecate and remove resumable bootstrap and decommission

Context: https://issues.apache.org/jira/browse/CASSANDRA-17679 >From the .yaml comment on the param I was working on adding: In certain environments, operators may want to disable resumable bootstrap in order to avoid potential correctness violations or data loss scenarios. Largely this centers

Cassandra project status update 2022-08-03

Greetings everyone! Let's check in on 4.1, see how we're doing: https://butler.cassandra.apache.org/#/ We had 4 failures on our last run. We've gone back and forth a bit with the CASTest failure, a test introduced back in CASSANDRA-12126 @Ignore'd, however that showed some legitimate failures