Re: [VOTE] Release Apache Cassandra 4.0.14
. > > The vote will be open for 96 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 artefact builds (JDK 8+11) - binary artefact runs (JDK 8+11) - debian package runs (JDK 8+11) - debian repo runs (JDK 8+11) - redhat* package runs (JDK 8+11) - redhat* repo runs (JDK 8+11)
Re: [VOTE] Release Apache Cassandra 4.1.7
. > > The vote will be open for 96 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 artefact builds (JDK 8+11) - binary artefact runs (JDK 8+11) - debian package runs (JDK 8+11) - debian repo runs (JDK 8+11) - redhat* package runs (JDK 8+11) - redhat* repo runs (JDK 8+11)
Re: [VOTE] Release Apache Cassandra 5.0.1
. > > The vote will be open for 96 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 correct - source artefact builds (JDK 11+17) - binary artefact runs (JDK 11+17) - debian package runs (JDK 11+17) - debian repo runs (JDK 11+17) - redhat* package runs (JDK11+17) - redhat* repo runs (JDK 11+17)
Re: [VOTE] Release Apache Cassandra 5.0.1
+1 Kind Regards, Brandon On Fri, Sep 20, 2024 at 9:36 AM Mick Semb Wever wrote: > > > Proposing the test build of Cassandra 5.0.1 for release. > > sha1: c206e4509003ac4cd99147d821bd4b5d23bdf5e8 > Git: https://github.com/apache/cassandra/tree/5.0.1-tentative > Maven Artifacts: > https://repository.apache.org/content/repositories/orgapachecassandra-1348/org/apache/cassandra/cassandra-all/5.0.1/ > > The Source and Build Artifacts, and the Debian and RPM packages and > repositories, are available here: > https://dist.apache.org/repos/dist/dev/cassandra/5.0.1/ > > == > This release introduces safeguards and observability into possible data loss > scenarios when nodes have a divergent view of the cluster. This happens > around edge-cases on unsafe bootstrapping, decommissions, or when a node has > a corrupted topology. Two configuration options have been added: > `log_out_of_token_range_requests` and `reject_out_of_token_range_requests`, > both enabled by default. The former will make nodes log requests they receive > that don't belong in their current or pending token ranges. The latter will > reject those requests, which prevents any eventual data loss that can occur > but may also incur small windows of degraded availability during range > movements. See CASSANDRA-13704 for further details. > == > > The vote will be open for 96 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]: CHANGES.txt: > https://github.com/apache/cassandra/blob/5.0.1-tentative/CHANGES.txt > [2]: NEWS.txt: > https://github.com/apache/cassandra/blob/5.0.1-tentative/NEWS.txt
[RESULT][VOTE] Release Apache Cassandra 4.0.14
Vote passes with three binding +1s ref: https://lists.apache.org/thread/lps6bskc1lr8f5bfhglystcmjdnqzn24 On Fri, 20 Sept 2024 at 16:35, Mick Semb Wever wrote: > > Proposing the test build of Cassandra 4.0.14 for release. > > sha1: 7bf67349579411521bcdee4febd209cff63179a6 > Git: https://github.com/apache/cassandra/tree/4.0.14-tentative > Maven Artifacts: > https://repository.apache.org/content/repositories/orgapachecassandra-1345/org/apache/cassandra/cassandra-all/4.0.14/ > > The Source and Build Artifacts, and the Debian and RPM packages and > repositories, are available here: > https://dist.apache.org/repos/dist/dev/cassandra/4.0.14/ > > == > This release introduces safeguards and observability into possible data > loss scenarios when nodes have a divergent view of the cluster. This > happens around edge-cases on unsafe bootstrapping, decommissions, or when a > node has a corrupted topology. Two configuration options have been added: > `log_out_of_token_range_requests` and > `reject_out_of_token_range_requests`, both enabled by default. The former > will make nodes log requests they receive that don't belong in their > current or pending token ranges. The latter will reject those requests, > which prevents any eventual data loss that can occur but may also incur > small windows of degraded availability during range movements. See > CASSANDRA-13704 for further details. > == > > The vote will be open for 96 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]: CHANGES.txt: > https://github.com/apache/cassandra/blob/4.0.14-tentative/CHANGES.txt > [2]: NEWS.txt: > https://github.com/apache/cassandra/blob/4.0.14-tentative/NEWS.txt >
[RESULT][VOTE] Release Apache Cassandra 4.1.7
Vote passes with five +1s, four binding. ref: https://lists.apache.org/thread/clq6959ntgltbpzx21xl1jkphcowwgg7 On Fri, 20 Sept 2024 at 16:35, Mick Semb Wever wrote: > > Proposing the test build of Cassandra 4.1.7 for release. > > sha1: ca494526025a480bc8530ed3ae472ce8c9cbaf7a > Git: https://github.com/apache/cassandra/tree/4.1.7-tentative > Maven Artifacts: > https://repository.apache.org/content/repositories/orgapachecassandra-1347/org/apache/cassandra/cassandra-all/4.1.7/ > > The Source and Build Artifacts, and the Debian and RPM packages and > repositories, are available here: > https://dist.apache.org/repos/dist/dev/cassandra/4.1.7/ > > == > This release introduces safeguards and observability into possible data > loss scenarios when nodes have a divergent view of the cluster. This > happens around edge-cases on unsafe bootstrapping, decommissions, or when a > node has a corrupted topology. Two configuration options have been added: > `log_out_of_token_range_requests` and > `reject_out_of_token_range_requests`, both enabled by default. The former > will make nodes log requests they receive that don't belong in their > current or pending token ranges. The latter will reject those requests, > which prevents any eventual data loss that can occur but may also incur > small windows of degraded availability during range movements. See > CASSANDRA-13704 for further details. > == > > The vote will be open for 96 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]: CHANGES.txt: > https://github.com/apache/cassandra/blob/4.1.7-tentative/CHANGES.txt > [2]: NEWS.txt: > https://github.com/apache/cassandra/blob/4.1.7-tentative/NEWS.txt >
[VOTE] Release Apache Cassandra Gocql Driver 1.7.0
Greetings all! I’m proposing the Cassandra Gocql Driver 1.7.0 for release. sha1: 953e0df999cabb3f5eef714df9921c00e9f632c2 git: https://github.com/apache/cassandra-gocql-driver/tree/v1.7.0-rc1 The Source release is available here: https://dist.apache.org/repos/dist/dev/cassandra/cassandra-gocql-driver/1.7.0/ This is the first release of the Gocql Driver since its donation. Developers will include this driver in their projects by specifying a commit hash or tag in go.mod rather than via the inclusion of binary artifacts so we’ve avoided the creation of binary artifacts completely. To avoid any premature access to this release before the vote is complete we’ve temporarily used the tag “v1.7.0-rc1” to clearly indicate that this tag points to a release candidate. Once the vote passes this tag will be updated to “v1.7.0”. 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. Thanks all! - Bret -
Re: CEP-15: Accord status
Sorry for the late reply > How would you recommend interested parties engage with reviewing this > behemoth? I am not fully sure. Previous when we talked about merging to trunk there was pushback that people needed time to look at things, so I want to make sure we give people plenty of time. The patch is large and could shrink a bit (as we keep rebasing against trunk some changes made may no longer be needed), but really any constructive feedback is welcome! > On Sep 23, 2024, at 8:08 AM, Caleb Rackliffe wrote: > > There is also a Jira to track pre-merge tasks here: > https://issues.apache.org/jira/browse/CASSANDRA-18196 > >> On Sep 20, 2024, at 4:09 PM, Josh McKenzie wrote: >> >> >>> >>> This presents an opportune moment for those interested to review the code. >>> ... >>> +88,341 −7,341 >>> 1003 Files changed >> >> O.o >> This is... very large. If we use CASSANDRA-8099 as our "banana for scale": >>> 645 files changed, 49381 insertions(+), 42227 deletions(-) >> >> To be clear - I don't think we collectively should be worried about >> disruption from this patch since: >> Each commit (or the vast majority?) has already been reviewed by >= 1 other >> committer >> 7.3k deletions is a lot less than 42k >> We now have fuzzing, property based testing, and the simulator >> Most of this code is additive >> How would you recommend interested parties engage with reviewing this >> behemoth? Or perhaps subsections of it or key areas to familiarize >> themselves with the structure? >> >> On Fri, Sep 20, 2024, at 12:17 PM, David Capwell wrote: >>> Recently, we rebased against the trunk branch, ensuring that the accord >>> branch is now in sync with the latest trunk version. This presents an >>> opportune moment for those interested to review the code. >>> >>> We have a pending pull request >>> (https://github.com/apache/cassandra/pull/3552) that we do not intend to >>> merge. >>> >>> Our current focus is on addressing several bug fixes and ensuring the >>> safety of topology changes (as evidenced by the number of issues filed >>> against the trunk). Once we wrap up bug fixes and safety features, we will >>> likely discuss the merge to trunk, so now is a great time to start engaging. >>> >>> Thank you everyone for your patience! >>
[RELEASE] Apache Cassandra 4.0.14 released
The Cassandra team is pleased to announce the release of Apache Cassandra version 4.0.14. Apache Cassandra is a fully distributed database. It is the right choice when you need scalability and high availability without compromising performance. http://cassandra.apache.org/ Downloads of source and binary distributions are listed in our download section: http://cassandra.apache.org/download/ This version is a bug fix release[1] on the 4.0 series. As always, please pay attention to the release notes[2] and Let us know[3] if you were to encounter any problem. == [WARNING] This release introduces safeguards and observability into possible data loss scenarios when nodes have a divergent view of the cluster. This happens around edge-cases on unsafe bootstrapping, decommissions, or when a node has a corrupted topology. Two configuration options have been added: `log_out_of_token_range_requests` and `reject_out_of_token_range_requests`, both enabled by default. The former will make nodes log requests they receive that don't belong in their current or pending token ranges. The latter will reject those requests, which prevents any eventual data loss that can occur but may also incur small windows of degraded availability during range movements. See CASSANDRA-13704 for further details. == Enjoy! [1]: CHANGES.txt https://github.com/apache/cassandra/blob/cassandra-4.0.14/CHANGES.txt [2]: NEWS.txt https://github.com/apache/cassandra/blob/cassandra-4.0.14/NEWS.txt [3]: https://issues.apache.org/jira/browse/CASSANDRA
[RELEASE] Apache Cassandra 4.1.7 released
The Cassandra team is pleased to announce the release of Apache Cassandra version 4.1.7. Apache Cassandra is a fully distributed database. It is the right choice when you need scalability and high availability without compromising performance. http://cassandra.apache.org/ Downloads of source and binary distributions are listed in our download section: http://cassandra.apache.org/download/ This version is a bug fix release[1] on the 4.1 series. As always, please pay attention to the release notes[2] and Let us know[3] if you were to encounter any problem. == [WARNING] This release introduces safeguards and observability into possible data loss scenarios when nodes have a divergent view of the cluster. This happens around edge-cases on unsafe bootstrapping, decommissions, or when a node has a corrupted topology. Two configuration options have been added: `log_out_of_token_range_requests` and `reject_out_of_token_range_requests`, both enabled by default. The former will make nodes log requests they receive that don't belong in their current or pending token ranges. The latter will reject those requests, which prevents any eventual data loss that can occur but may also incur small windows of degraded availability during range movements. See CASSANDRA-13704 for further details. == Enjoy! [1]: CHANGES.txt https://github.com/apache/cassandra/blob/cassandra-4.1.7/CHANGES.txt [2]: NEWS.txt https://github.com/apache/cassandra/blob/cassandra-4.1.7/NEWS.txt [3]: https://issues.apache.org/jira/browse/CASSANDRA
