A release is always coming ;) I'll try to get the 4.1.6 ball rolling on Monday.
Kind Regards, Brandon On Wed, Jul 24, 2024 at 3:56 PM Elliott Sims via dev <dev@cassandra.apache.org> wrote: > > Looks like this is out and there's a 5.0-rc release. Is a 4.1.6 release with > a fix for CASSANDRA-19668 coming? > > On Sat, Jun 29, 2024 at 2:39 AM Mick Semb Wever <m...@apache.org> wrote: >> >> >> The votes fails with a veto in place having made CASSANDRA-19668 an 5.0-rc >> blocker. >> >> Once 19668 lands we will need an immediate release of 4.1.6 too. >> >> >> >> On Fri, 28 Jun 2024 at 06:49, Jon Haddad <j...@jonhaddad.com> wrote: >>> >>> Thanks for confirming this, Blake. I agree that we should not knowingly >>> ship new versions with severe bugs that cause the DB to crash, regression >>> or not. >>> >>> -1 from me as well >>> >>> >>> On Fri, Jun 28, 2024 at 1:39 AM Blake Eggleston <beggles...@apple.com> >>> wrote: >>>> >>>> Looking at the ticket, I’d say Jon’s concern is legitimate. The segfaults >>>> Jon is seeing are probably caused by paxos V2 when combined with off heap >>>> memtables for the reason Benedict suggests in the JIRA. This problem will >>>> continue to exist in 5.0. Unfortunately, it looks like the patch posted is >>>> not enough to address the issue and will need to be a bit more involved to >>>> properly fix the problem. >>>> >>>> While this is not a regression, I think Jon’s point about trie memtables >>>> increasing usage of off heap memtables is a good one, and anyway we >>>> shouldn’t be doing major releases with known process crashing bugs. >>>> >>>> So I’m voting -1 on this release and will work with Jon and Benedict to >>>> get this fixed. >> >> >> >> > > > This email, including its contents and any attachment(s), may contain > confidential and/or proprietary information and is solely for the review and > use of the intended recipient(s). If you have received this email in error, > please notify the sender and permanently delete this email, its content, and > any attachment(s). Any disclosure, copying, or taking of any action in > reliance on an email received in error is strictly prohibited.
