[ 
https://issues.apache.org/jira/browse/ROCKETMQ-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16364051#comment-16364051
 ] 

Sohaib Iftikhar commented on ROCKETMQ-124:
------------------------------------------

This looks super interesting! Is there a dev channel where we can discuss this?

> 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
>              Labels: gsoc2018
>
> The duplicated messages are worrisome. It will cost much if the user needs 
> non-repeating messages.
> In most cases, the user need store the consumer 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.
> 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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to