[RIP-43]Support Timing Messages with Arbitrary Time Delay

[GenerousMan]

Currently, RocketMQ's timing message feature only supports delayed delivery for specific time levels. Such timing message feature(only support specific levels of delay time) is no longer enough to support the flexible usage of rocketmq. Therefore, we need a timing message feature that supports arbitrary delay time.

1. Please describe the feature you are requesting. a. Support timing messages with arbitrary time delays. b. Provide reliable storage for timing messages. c. Ensure that there is reliable sending performance for timing messages. d. Provide observability troubleshooting capabilities for timing messages.

2. Provide any additional detail. I have written my proposal on the link below： Google Doc: https://docs.google.com/document/d/1D6XWwY39p531c2aVi5HQll9iwzTUNT1haUFHqMoRkT0/edit?usp=sharing Shimo:https://shimo.im/docs/gXqme9PKKpIeD7qo/

Welcome any discussion on this proposal.

[sunheyi6]

fix #4558

[Inuyasha-Monster]

in doc , some words are wrong.. that are confusing me the letter e -> d

[GenerousMan]

in doc , some words are wrong.. that are confusing me the letter e -> d

OMG, you are right. I'll change it in the doc. Sorry.

[GenerousMan]

Here is a performance report of timing message, which is tested in a 32C 128G SSD machine. The report for machine with lower configuration is still on the way.... Timing Message Performance Report.pdf

[lizhanhui]

@GenerousMan Can we make the report a blog in rocketmq-site? It would remain valuable for future engineers when they perform evaluations.

[GenerousMan]

@GenerousMan Can we make the report a blog in rocketmq-site? It would remain valuable for future engineers when they perform evaluations.

Of course. I will create a .md file and put it into this website.

[GenerousMan]

Here is a new report, which is made in a 16C 32GB machine(ESSD).

Timing Message Performance Report(16C 32G 1T ESSD).pdf

[github-actions[bot]]

This issue is stale because it has been open for 365 days with no activity. It will be closed in 3 days if no further activity occurs.

[github-actions[bot]]

This issue was closed because it has been inactive for 3 days since being marked as stale.