-
Notifications
You must be signed in to change notification settings - Fork 11.8k
[Feature] Support recalling of delay message #8974
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
Comments
imzs
added a commit
to imzs/rocketmq
that referenced
this issue
Nov 22, 2024
imzs
added a commit
to imzs/rocketmq
that referenced
this issue
Nov 22, 2024
imzs
added a commit
to imzs/rocketmq
that referenced
this issue
Nov 28, 2024
…on test, disable polling and wait more time.
imzs
added a commit
to imzs/rocketmq
that referenced
this issue
Nov 28, 2024
…t test, exclude from bazel test.
imzs
added a commit
to imzs/rocketmq
that referenced
this issue
Dec 2, 2024
…n case of rare uk collision
imzs
added a commit
to imzs/rocketmq
that referenced
this issue
Dec 2, 2024
lollipopjin
pushed a commit
that referenced
this issue
Dec 9, 2024
imzs
added a commit
to imzs/rocketmq
that referenced
this issue
Dec 19, 2024
lizhimins
pushed a commit
that referenced
this issue
Dec 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is Your Feature Request Related to a Problem?
.
Describe the Solution You'd Like
As the timer wheel implementation of delay message, we've reserved a cancellation ability: recalling scheduled messages by sending a corresponding delete message. However, we have not exposed an API to the upper layer. Some developers may construct and send a special message to achieve this, but this is not a friendly and sustainable solution because:
Therefore, the first step is to provide a user-friendly API to implement this feature.
recallMessage(topic, handle)
, recall handle from sending result is a bit like ReceiptHandle, containing information such as ID, broker, and timestamp.Describe Alternatives You've Considered
.
Additional Context
.
The text was updated successfully, but these errors were encountered: