You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@rocketmq.apache.org by "vongosling (JIRA)" <ji...@apache.org> on 2017/12/13 12:00:00 UTC
[jira] [Closed] (ROCKETMQ-124) Support non-redundant message
delivery mechanism
[ https://issues.apache.org/jira/browse/ROCKETMQ-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
vongosling closed ROCKETMQ-124.
-------------------------------
Resolution: Feedback Received
Fix Version/s: (was: 4.2.0)
> 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
>
> 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.4.14#64029)