3424672656 opened a new issue, #9141: URL: https://github.com/apache/rocketmq/issues/9141
### Before Creating the Enhancement Request - [x] I have confirmed that this should be classified as an enhancement rather than a bug/feature. ### Summary We will use rocksdb's time wheel support to implement arbitrary delayed messages, solve the problem of cold read and metric imprecision caused by large-scale delayed messages, and support timely deletion and more accurate latency levels and other features ### Motivation We have encountered some problems in the actual production environment, and have been troubled by these problems. In large-scale timed message scenarios, frequent reading of old files reduces the read rate, increases the delay of delayed messages, and causes problems such as inaccurate observation and delay. Meanwhile, functions such as preheating of file version suffer large losses. Therefore, the introduction of rocksdb can avoid the impact of cold read, provide more accurate index calculation, and support longer timed messages. Provide more precise latency levels, but we still need to ensure message write performance and read performance and latency, etc. Detailed design: https://shimo.im/docs/913JMO8ZoJugwEAE ### Describe the Solution You'd Like The proposal addresses two main issues: 1. Cold read problem caused by large-scale timed messages 2. Delete messages and metric inaccuracies when messages are sent out Extra can support more optimizations 1. Delete messages in a timely manner 2. Messages can be preheated and more precise timing can be supported, such as supporting the millisecond level ### Describe Alternatives You've Considered no ### Additional Context _No response_ -- 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: commits-unsubscr...@rocketmq.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
