Hi Scott, just put -1 on the voting threads for 4.1 and 5.0 to have it formal.
Regards On Tue, Jul 14, 2026 at 6:48 PM Ekaterina Dimitrova <[email protected]> wrote: > > I agree with that too. Thank you, Scott for bringing it to the list! > > On Tue, 14 Jul 2026 at 12:46, Brandon Williams <[email protected]> wrote: >> >> It makes sense to me. As far as I know there's nothing urgent driving >> the currently proposed releases, so I support re-rolling for these >> more serious bugs. >> >> Kind Regards, >> Brandon >> >> On Tue, Jul 14, 2026 at 11:40 AM C. Scott Andreas <[email protected]> >> wrote: >> > >> > Hi everyone, >> > >> > TLDR: I propose we hold and re-roll 4.1+ releases under vote due to a >> > newly-identified critical data loss bug. >> > >> > On Saturday, a critical bug surfaced dating back to 4.1.6 that requires an >> > urgent release from the project: >> > https://issues.apache.org/jira/browse/CASSANDRA-21508: Coordinator >> > load-shedding returns OverloadedException without setting streamId, >> > misrouting query responses >> > >> > In short, requests that trip native_transport_timeout result in responses >> > being sent to clients on the incorrect streamId. This causes query >> > responses to become incorrectly associated with different queries. Clients >> > may observe deserialization failures, nonsensical responses, or responses >> > containing data from other queries. >> > >> > There is no reasonable config mitigation to guard against this issue. It >> > requires urgent attention from the project, and patches will be available >> > for 4.1.x, 5.0.x, 6.0, and trunk shortly. Please see the ticket for >> > details. >> > >> > There is a second less-critical but still important corruption bug >> > identified in SAI. This issue is: >> > https://issues.apache.org/jira/browse/CASSANDRA-21516: SAI Component >> > Checksum Validation Should be Segment-Aware >> > >> > This issue can result in SAI indexes reporting as corrupt and unqueryable >> > due to incorrect checksum validation. However the indexes can be rebuilt >> > so the impact is availability rather than corruption / data loss. >> > >> > Patches should be committed for both of these issues within the week. >> > >> > – Scott >> > >> >
