[jira] [Commented] (ROCKETMQ-124) Support non-redundant message delivery mechanism
[ https://issues.apache.org/jira/browse/ROCKETMQ-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389890#comment-16389890 ] Sohaib Iftikhar commented on ROCKETMQ-124: -- Just adding the link to the [design doc|https://docs.google.com/document/d/1KSpXGNDH0HF5E27lfKJxJnjIjPtlP1Q-M6rj3yZde24] here to sync up with the dev discussion. Also helps with more reviews/feedback on it. > 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)
[jira] [Commented] (ROCKETMQ-124) Support non-redundant message delivery mechanism
[ https://issues.apache.org/jira/browse/ROCKETMQ-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16376274#comment-16376274 ] Lahiru Jayathilake commented on ROCKETMQ-124: - Hi vongosling I went through the documentation and currently, I am trying the examples listed under https://rocketmq.apache.org/ to get an idea about the RocketMQ. Same time I am going through the code base for understanding. And also I have already subscribed to the dev mailing list. These took little longer because I had my end semester exams last week. Hope I am on the right track. Any guidance would be very helpful. Thanks :) > 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)
[jira] [Commented] (ROCKETMQ-124) Support non-redundant message delivery mechanism
[ https://issues.apache.org/jira/browse/ROCKETMQ-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16368811#comment-16368811 ] Lahiru Jayathilake commented on ROCKETMQ-124: - Hi, I am Lahiru Jayathilake, a final year undergraduate from Computer Science and Engineering Department, University of Moratuwa. I am looking forward to participating in GSoC 2018, and I am interested in this project. I have already started to go through the documentation and to set-up the dev environment. > 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)
[jira] [Commented] (ROCKETMQ-124) Support non-redundant message delivery mechanism
[ https://issues.apache.org/jira/browse/ROCKETMQ-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16366797#comment-16366797 ] yukon commented on ROCKETMQ-124: Hi [~sohaibiftikhar], please refer to here: http://rocketmq.apache.org/about/contact/ > 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)
[jira] [Commented] (ROCKETMQ-124) Support non-redundant message delivery mechanism
[ 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)
