tolbertam commented on code in PR #4558: URL: https://github.com/apache/cassandra/pull/4558#discussion_r2837082147
########## NEWS.txt: ########## @@ -68,12 +68,37 @@ using the provided 'sstableupgrade' tool. 5.0.7 ====== +New features +------------ + - CEP-37 Auto Repair is a fully automated scheduler that provides repair orchestration within Apache Cassandra. This + significantly reduces operational overhead by eliminating the need for operators to deploy external tools to submit + and manage repairs. See + https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-37+Apache+Cassandra+Unified+Repair+Solution for more + details on the motivation and design. + Upgrading --------- - This release addresses a security vulnerability in the LZ4 dependency, documented in CASSANDRA-21052. For users who did not use LZ4 native libraries, this will now fallback to a safer but less performant pure Java implementation. During startup, a warning will be logged if the LZ4 native library is not available. + - The auto-repair feature requires enabling the JVM property `cassandra.autorepair.enable=true` (add + `-Dcassandra.autorepair.enable=true` to JVM options) before starting the node. This property creates the required + schema elements for auto-repair, including the auto_repair column in system_schema.tables and system_schema.views, + as well as the auto_repair_history and auto_repair_priority tables in system_distributed. After enabling this + property, you still need to enable auto-repair scheduling either in cassandra.yaml under the `auto_repair` section + or at runtime via JMX. + + Users who do not intend to use auto-repair can leave this property disabled (the default) to maintain schema + compatibility with pre-5.0.7 nodes during rolling upgrades. This property must be set consistently across all + nodes before startup and cannot be changed at runtime. + + WARNING: This property is non-reversible. Once enabled, it cannot be disabled. Attempting to start a node + with `cassandra.autorepair.enable=false` after it was previously enabled will cause the node to fail during + initialization due to schema incompatibility (the persisted schema contains auto-repair columns that are not + recognized when the property is disabled). To disable auto-repair scheduling after the property has been + enabled, use cassandra.yaml or JMX instead of changing the JVM property. Review Comment: :+1: great write up here, does a good job describing how to opt into feature and describing how it mitigates any risk if you do no opt into it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
