-
Notifications
You must be signed in to change notification settings - Fork 11.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ROCKETMQ-309] Add new consumer implement #190
Conversation
Did you mean BTW, could you please report a JIRA issue before submitting a pull request? |
@zhouxinyu ,sorry I have modify my commented again . |
I have report JIRA ISSUE(309), would you have check ? @zhouxinyu |
Thanks, let's discuss in ROCKETMQ-309 first~ |
even if the apps do not run in the docker, it also has the problem. |
what about the result of this pull request? @zhouxinyu |
Yes, It's exactly expected, Consume from the last offset for each restart isn't common. |
@lyy4j When using Broadcast Model , offset is stored in local. If you are using docker,please map volume offset store directory to host. |
@zhouxinyu |
---for old consumers, they would use last offset when every restart, right?
it's right.
---for new consumers, they would use offset=0. it means new consumers will
consume all messages the broker have got since it start, am i right?
Should from max offset, not 0.
…On Fri, Jun 8, 2018 at 12:07 AM, francis lee ***@***.***> wrote:
@zhouxinyu <https://github.com/zhouxinyu>
when CONSUME_FROM_LAST_OFFSET is set ,
for old consumers, they would use last offset when every restart, right?
for new consumers, they would use offset=0. it means new consumers will
consume all messages the broker have got since it start, am i right?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#190 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ACeujcWPW59NBdBiQb8uZDaXbUPSalUKks5t6U-2gaJpZM4QPkAm>
.
|
1) HA ScheduleMessage deliver two times, timer cancel() can't terminate running task.
When application use consume client in Broadcast model which runs in the docker,we can pull message only from fist offset, because docker allocate the apps at random and cause the store file do not reuse. However, we only want to pull message from last offset sometimes even though the apps runs in the docker, and we can use MQBroadcastFromLastConsumer in this case.