[
https://issues.apache.org/jira/browse/ROCKETMQ-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dongeforever updated ROCKETMQ-124:
----------------------------------
Fix Version/s: 4.2.0-incubating
> Support non-redundant message delivery mechanism
> ------------------------------------------------
>
> Key: ROCKETMQ-124
> URL: https://issues.apache.org/jira/browse/ROCKETMQ-124
> Project: Apache RocketMQ
> Issue Type: Wish
> Components: rocketmq-broker, rocketmq-client, rocketmq-store
> Reporter: yukon
> Priority: Minor
> Fix For: 4.2.0-incubating
>
>
> The duplicated messages are worrisome. It will cost much if user need
> non-repeating messages.
> In most cases, user need store the consume records to judge a message is
> replicated or not, and the store stage should guarantee strong consistency.
> As you see, it's very complicated, so support a strict and non-redundant
> message delivery mechanism is impending.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
