Re: Road to 5.0-GA (was: [VOTE] Release Apache Cassandra 5.0-alpha2)

We were able to narrow it down, and it seems that both issues have been introduced by [1] (both tests pass without this commit). There is a preliminary fix, and we're working on a minimal repro. Please track [2] for more information and latest updates. [1] https://github.com/apache/cassandra/co

Re: Road to 5.0-GA (was: [VOTE] Release Apache Cassandra 5.0-alpha2)

er 6, 2023 11:40 > To: dev@cassandra.apache.org > Subject: Re: Road to 5.0-GA (was: [VOTE] Release Apache Cassandra > 5.0-alpha2) > > NetApp Security WARNING: This is an external email. Do not click links or > open attachments unless you recognize the sender and know the content is >

Re: Road to 5.0-GA (was: [VOTE] Release Apache Cassandra 5.0-alpha2)

The link is fixed. Thanks! From: Miklosovic, Stefan Sent: Monday, November 6, 2023 11:42 To: dev@cassandra.apache.org Subject: Re: Road to 5.0-GA (was: [VOTE] Release Apache Cassandra 5.0-alpha2) I can't view it e

Re: Road to 5.0-GA (was: [VOTE] Release Apache Cassandra 5.0-alpha2)

I can't view it either. From: guo Maxwell Sent: Monday, November 6, 2023 11:40 To: dev@cassandra.apache.org Subject: Re: Road to 5.0-GA (was: [VOTE] Release Apache Cassandra 5.0-alpha2) NetApp Security WARNING: This is an external email. Do not

Re: Road to 5.0-GA (was: [VOTE] Release Apache Cassandra 5.0-alpha2)

Do I need permission to view this link? When I open it, an error appears, saying “It may have been deleted or you don't have permission to view it.” Benjamin Lerer 于2023年11月6日周一 18:34写道： > I created a Dashboard to track the progress and remaining tasks for 5.0: > https://issues.apache.org/jira/s

Re: Road to 5.0-GA (was: [VOTE] Release Apache Cassandra 5.0-alpha2)

I created a Dashboard to track the progress and remaining tasks for 5.0: https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=593 Everybody logged in should have access. Ping me if it is not the case. Le sam. 4 nov. 2023 à 19:54, Mick Semb Wever a écrit : > > Please mark such bugs wit

Re: [VOTE] Release Apache Cassandra 5.0-alpha2

Nice, thanks for the quick fix! Checked and working now. On Sat, 4 Nov 2023 at 21:11 Mick Semb Wever wrote: > > > On Sun, 5 Nov 2023 at 00:49, Paulo Motta wrote: > >> > With the publication of this release I would like to switch the >> default 'latest' docs on the website from 4.1 to 5.0. Are

Re: [VOTE] Release Apache Cassandra 5.0-alpha2

On Sun, 5 Nov 2023 at 00:49, Paulo Motta wrote: > > With the publication of this release I would like to switch the default > 'latest' docs on the website from 4.1 to 5.0. Are there any objections to > this ? > > It looks like the switch of latest to 5.0 broken some top search links > (returns

Re: [VOTE] Release Apache Cassandra 5.0-alpha2

> With the publication of this release I would like to switch the default 'latest' docs on the website from 4.1 to 5.0. Are there any objections to this ? It looks like the switch of latest to 5.0 broken some top search links (returns 404 to me): [1] - https://www.google.com/search?q=apache+cas

Re: Road to 5.0-GA (was: [VOTE] Release Apache Cassandra 5.0-alpha2)

Please mark such bugs with fixVersion 5.0-beta If there are no more tickets that need API changes (i.e. those that should be marked fixVersion 5.0-alpha) this then indicates we do not need a 5.0-alpha3 release and can focus towards 5.0-beta1 (regardless of having blockers open to it). Appreciate

Re: [VOTE] Release Apache Cassandra 5.0-alpha2

1. “No objections from me since these issues are mostly cosmetic, but it would be nice to clear these before the next alpha/beta. I will create a ticket for the unknown module warning later if nobody beats me to it.” 1. 1. CASSANDRA-19001

Re: Road to 5.0-GA (was: [VOTE] Release Apache Cassandra 5.0-alpha2)

Yep, data loss bugs are not any old bug. I’m concretely -1 (binding) releasing a beta with one that’s either under investigation or confirmed.As Scott says, hopefully it won’t come to that - the joy of deterministic testing is this should be straightforward to triage.On 4 Nov 2023, at 17:30, C. Sco

Re: Road to 5.0-GA (was: [VOTE] Release Apache Cassandra 5.0-alpha2)

I’d happily be the first to vote -1(nb) on a release containing a known and reproducible bug that can result in data loss or an incorrect response to a query. And I certainly wouldn’t run it.Since we have a programmatic repro within just a few seconds, this should not take long to root-cause.On Fri

Re: Road to 5.0-GA (was: [VOTE] Release Apache Cassandra 5.0-alpha2)

> I think before we cut a beta we need to have diagnosed and fixed 18993 > (assuming it is a bug). Before a beta? I could see that for rc or GA definitely, but having a known (especially non-regressive) data loss bug in a beta seems like it's compatible with the guarantees we're providing for it

Re: Road to 5.0-GA (was: [VOTE] Release Apache Cassandra 5.0-alpha2)

Totally agree with the others. Such an issue on its own should be a priority in any release. Looking forward to the reproduction test mentioned on the ticket. Thanks to Alex for his work on harry! On Sat, 4 Nov 2023 at 12:47, Benedict wrote: > Alex can confirm but I think it actually turns out

Re: Road to 5.0-GA (was: [VOTE] Release Apache Cassandra 5.0-alpha2)

Alex can confirm but I think it actually turns out to be a new bug in 5.0, but either way we should not cut a release with such a serious potential known issue. > On 4 Nov 2023, at 16:18, J. D. Jordan wrote: > > Sounds like 18993 is not a regression in 5.0? But present in 4.1 as well? > So

Re: Road to 5.0-GA (was: [VOTE] Release Apache Cassandra 5.0-alpha2)

Sounds like 18993 is not a regression in 5.0? But present in 4.1 as well? So I would say we should fix it with the highest priority and get a new 4.1.x released. Blocking 5.0 beta voting is a secondary issue to me if we have a “data not being returned” issue in an existing release? > On Nov 4,

Re: Road to 5.0-GA (was: [VOTE] Release Apache Cassandra 5.0-alpha2)

I agree and just now opened it for 5.0-beta (among others.) Kind Regards, Brandon On Sat, Nov 4, 2023 at 11:08 AM Benedict wrote: > > I think before we cut a beta we need to have diagnosed and fixed 18993 > (assuming it is a bug). > > > On 4 Nov 2023, at 16:04, Mick Semb Wever wrote: > > > > 

Re: Road to 5.0-GA (was: [VOTE] Release Apache Cassandra 5.0-alpha2)

I think before we cut a beta we need to have diagnosed and fixed 18993 (assuming it is a bug). > On 4 Nov 2023, at 16:04, Mick Semb Wever wrote: > >  >> >> With the publication of this release I would like to switch the >> default 'latest' docs on the website from 4.1 to 5.0. Are there any >

Road to 5.0-GA (was: [VOTE] Release Apache Cassandra 5.0-alpha2)

> With the publication of this release I would like to switch the > default 'latest' docs on the website from 4.1 to 5.0. Are there any > objections to this ? I would also like to propose the next 5.0 release to be 5.0-beta1 With the aim of reaching GA for the Summit, I would like to suggest we

Re: [VOTE] Release Apache Cassandra 5.0-alpha2

> > > As this is alpha release - can we open a ticket to be resolved in the > next alpha/beta? It is up to PMC to decide, of course. > > No objections from me since these issues are mostly cosmetic, but it would > be nice to clear these before the next alpha/beta. I will create a ticket > for the u

[RESULT][VOTE] Release Apache Cassandra 5.0-alpha2

> The vote will be open for 72 hours (longer if needed). Everyone who > has tested the build is invited to vote. Votes by PMC members are > considered binding. A vote passes if there are at least three binding > +1s and no -1's. The vote passes with 6 +1s (three binding). With the publication

Re: [VOTE] Release Apache Cassandra 5.0-alpha2

Thanks Ekaterina! I think the security manager ticket is CASSANDRA-18711 (correct me if I’m wrong) - sorry missed this in my previous search. > As this is alpha release - can we open a ticket to be resolved in the next alpha/beta? It is up to PMC to decide, of course. No objections from me since

Re: [VOTE] Release Apache Cassandra 5.0-alpha2

I am sorry, I totally forgot to address your other concern, Paulo. The security manager is marked for deprecation in JDK 17. So this warning is to stress to people they need to take care of a replacement, sooner than later. I believe we have somewhere an unassigned ticket in Open status to address

Re: [VOTE] Release Apache Cassandra 5.0-alpha2

Hi Paulo, Thank you for testing and for raising the issue! I can confirm I do not use the same JDK as you, and I did not see any warnings on my machine on startup or when calling nodetool commands. I believe on a quick check that jdk.attach was needed for nodetool sjk. (It was mentioned on CASSAN

Re: [VOTE] Release Apache Cassandra 5.0-alpha2

Clarification: - When running nodetool only the "Unknown module" warnings show up. All warnings show up during startup. On Fri, Nov 3, 2023 at 7:58 PM Paulo Motta wrote: > Launched a tarball-based 5.0-alpha2 container on top of > "eclipse-temurin:17-jre-focal" and the server starts up fine, can

Re: [VOTE] Release Apache Cassandra 5.0-alpha2

Launched a tarball-based 5.0-alpha2 container on top of "eclipse-temurin:17-jre-focal" and the server starts up fine, can run nodetool and cqlsh. I got these seemingly harmless JDK17 warnings during startup and when running nodetool (no warnings on JDK11): WARNING: Unknown module: jdk.attach spec

Re: [VOTE] Release Apache Cassandra 5.0-alpha2

+1 On Mon, Oct 30, 2023 at 3:47 PM Mick Semb Wever wrote: > Proposing the test build of Cassandra 5.0-alpha2 for release. > > DISCLAIMER, this alpha release does not contain the features: > Transactional Cluster Metadata (CEP-21) and Accord Transactions > (CEP-15). These features are under disc

Re: [VOTE] Release Apache Cassandra 5.0-alpha2

+1 Kind Regards, Brandon On Mon, Oct 30, 2023 at 4:47 PM Mick Semb Wever wrote: > > Proposing the test build of Cassandra 5.0-alpha2 for release. > > DISCLAIMER, this alpha release does not contain the features: > Transactional Cluster Metadata (CEP-21) and Accord Transactions > (CEP-15). These

Re: [EXTERNAL] Re: [VOTE] Release Apache Cassandra 5.0-alpha2

__ >> From: Mick Semb Wever >> Sent: Tuesday, October 31, 2023 1:43 PM >> Cc: dev >> Subject: [EXTERNAL] Re: [VOTE] Release Apache Cassandra 5.0-alpha2 >> >> > The vote will be open for 72 hours (longer if needed). Everyone who >> > has test

Re: [EXTERNAL] Re: [VOTE] Release Apache Cassandra 5.0-alpha2

t; *Subject:* [EXTERNAL] Re: [VOTE] Release Apache Cassandra 5.0-alpha2 > > > The vote will be open for 72 hours (longer if needed). Everyone who > > has tested the build is invited to vote. Votes by PMC members are > > considered binding. A vote passes if there are at l

Re: [EXTERNAL] Re: [VOTE] Release Apache Cassandra 5.0-alpha2

+1 Heck, yeah, we already tested the branch (build ourselves) and it works great so far. From: Mick Semb Wever Sent: Tuesday, October 31, 2023 1:43 PM Cc: dev Subject: [EXTERNAL] Re: [VOTE] Release Apache Cassandra 5.0-alpha2 > The vote will be open for

Re: [VOTE] Release Apache Cassandra 5.0-alpha2

> The vote will be open for 72 hours (longer if needed). Everyone who > has tested the build is invited to vote. Votes by PMC members are > considered binding. A vote passes if there are at least three binding > +1s and no -1's. +1 Checked - signing correct - checksums are correct - source artef

[VOTE] Release Apache Cassandra 5.0-alpha2

Proposing the test build of Cassandra 5.0-alpha2 for release. DISCLAIMER, this alpha release does not contain the features: Transactional Cluster Metadata (CEP-21) and Accord Transactions (CEP-15). These features are under discussion to be pushed to a 5.1-alpha1 release, with an eta still this ye