Aaron-He opened a new issue #2289: URL: https://github.com/apache/rocketmq/issues/2289
At present, RocketMQ only supports delay messages with fixed delay levels(1s 5s 10s 30s 1m 2m 3m 4m 5m 6m 7m 8m 9m 10m 20m 30m 1h 2h), which is not flexible enough. Current delay message process diagram:  The current delay message design is realized by using new separate Topic(SCHEDULE_TOPIC_XXXX) and Queue, if we want to achieve any time delay of seconds within 40 days, based on the current solution, 40 * 24 * 60 * 60 = 345600 Queues are needed, and the cost is very high. Also, the message cannot be delayed too long because the CommitLog will be deleted after a fixed amount of hours (default 48 hours). In order to meet the requirements of flexible time delay messages, we can redesign the architecture of delay messages(different from the current delay message, the delay message here refers to the message delivered at a specific time or delayed a period time) and introduce [Time Wheel](http://www.cs.columbia.edu/~nahum/w6998/papers/sosp87-timing-wheels.pdf). ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
