Hey Pranav, Recently, the repair framework has been automated as part of CEP-37 <https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-37%3A+Apache+Cassandra+Unified+Repair+Solution>. But many improvements need to be made to cover other aspects of Apache Cassandra cluster lifecycle, such as automatically stopping the scheduler if a new DC is added, triggering the framework if the keyspace's replication factor changes, etc. Here are some of the unassigned tickets under epic (CASSANDRA-19918 <https://issues.apache.org/jira/browse/CASSANDRA-19918>)
- CASSANDRA-20414 <https://issues.apache.org/jira/browse/CASSANDRA-20414> - CASSANDRA-20582 <https://issues.apache.org/jira/browse/CASSANDRA-20582> There is also a dedicated ASF Slack channel ( *#cassandra-repair-scheduling-cep37*) where we discuss some of the tasks. I'd be happy to hop on a call to update you on our current status and outline our plans for the next few months. Let me know! Jaydeep On Sat, Jul 5, 2025 at 11:27 PM pranav shenoy <pranavsheno...@gmail.com> wrote: > Hi all, > > I've recently been contributing to Cassandra by working on some bugs in > Accord, and I’m now looking to pick up my next tasks. > > While I’ve been browsing through JIRA, I find it a bit challenging to > identify suitable tasks just based on the brief descriptions, as I’m still > getting up to speed with the project. I was wondering if anyone could > kindly point me toward tasks that I can pick - possibly beyond bug fixes. > > Also, I’d love to get a better understanding of the ongoing feature work > or broader efforts that contributors are currently focusing on, in case > there’s an opportunity to get involved. > > Thanks in advance for your guidance! > > Best regards, > > Pranav Shenoy >
