[
https://issues.apache.org/jira/browse/ROCKETMQ-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lahiru Jayathilake updated ROCKETMQ-124:
----------------------------------------
Comment: was deleted
(was: [~lahiruj]
How are things going ?
I would like to help you for this topic in the CSoC, If you have any technical
question, we could also use the RocketMQ dev email[1] list to discuss.
[1]http://rocketmq.apache.org/about/contact/
p.s. you could subscribe our Development channel on my provided button)
> 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)
