RongtongJin opened a new issue, #9666: URL: https://github.com/apache/rocketmq/issues/9666
### Before Creating the Enhancement Request - [x] I have confirmed that this should be classified as an enhancement rather than a bug/feature. ### Summary This feature implements an accelerated startup recovery mechanism specifically designed for RocksDB-based storage configurations using SYNC_FLUSH. This enhancement leverages existing ConsumeQueue information to intelligently skip unnecessary scanning and directly position to the recovery starting point. ### Motivation In production environments with large-scale message storage using RocksDB and SYNC_FLUSH configuration, the broker startup recovery process can take significant time due to sequential scanning of commit log files. This impacts system availability and recovery time objectives (RTO) in scenarios such as: - System restarts after maintenance - Recovery from unexpected shutdowns - Cluster scaling operations - Disaster recovery scenarios ### Describe the Solution You'd Like Implement an optional accelerated recovery feature that: 1. **Configuration Control**: Add enableAcceleratedRecovery boolean configuration option (default: false) 2. **Intelligent Recovery**: Utilize RocksDB ConsumeQueue MAX_PHYSICAL_OFFSET to determine recovery starting positions ### Describe Alternatives You've Considered No ### Additional Context No -- 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]
