Hi all, only dummy question, sorry for that. Is it enough to open only issue (e.g. this [CASSANDRA-19971] CRC mismatch - ASF JIRA (apache.org)<https://issues.apache.org/jira/browse/CASSANDRA-19971>) or it is useful/necessary to switch the issue to a specific state or assign to relevant role/person? Thx for advice
J. Steuer This item's classification is Internal. It was created by and is in property of the Home Credit. Do not distribute outside of the organization. From: Mick Semb Wever <m...@apache.org> Sent: Monday, September 30, 2024 8:37 PM To: user@cassandra.apache.org; dev <d...@cassandra.apache.org> Subject: [External][RELEASE] Apache Cassandra 5.0.1 released This message is from an EXTERNAL SENDER - be CAUTIOUS, particularly with links and attachments. Please report all suspicious e-mails to helpd...@embedit.com<mailto:helpd...@embedit.com> ________________________________ The Cassandra team is pleased to announce the release of Apache Cassandra version 5.0.1. 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 5.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-5.0.1/CHANGES.txt [2]: NEWS.txt https://github.com/apache/cassandra/blob/cassandra-5.0.1/NEWS.txt [3]: https://issues.apache.org/jira/browse/CASSANDRA
