Details
-
Wish
-
Status: Closed
-
Major
-
Resolution: Abandoned
-
None
Description
The duplicated messages will impose the extra cost if the user needs non-repeating messages.
In most cases, the user needs to store the consumer records to determine if a message is duplicated, and the store stage should guarantee consistency. So we need to support a strict and non-redundant message delivery mechanism.
In this context, we hope to design a delivery once plugin, say, you could design a global(but need raft guarantee multi-copy data) storage, using the hooker of RocketMQ ConsumeMessageHook to finish the task.