You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@rocketmq.apache.org by GitBox <gi...@apache.org> on 2021/09/03 05:56:22 UTC
[GitHub] [rocketmq] coder-zzzz opened a new issue #3316: [NEW FEATURE]BROADCASTING consumer's consume detail is empty
coder-zzzz opened a new issue #3316:
URL: https://github.com/apache/rocketmq/issues/3316
When use BROADCASTING mode, offset only store on the machine which consumer is running on. Admin must login every machine to find out what offset it is . It will make hard for analyzing some problems.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq] ShannonDing commented on issue #3316: [NEW FEATURE]BROADCASTING consumer's consume detail is empty
Posted by GitBox <gi...@apache.org>.
ShannonDing commented on issue #3316:
URL: https://github.com/apache/rocketmq/issues/3316#issuecomment-916708351
maybe you can have a try on other solution: using different cluster consumer ids under cluster model instead of broadcast...
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq] vongosling closed issue #3316: [NEW FEATURE]BROADCASTING consumer's consume detail is empty
Posted by GitBox <gi...@apache.org>.
vongosling closed issue #3316:
URL: https://github.com/apache/rocketmq/issues/3316
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq] RongtongJin commented on issue #3316: [NEW FEATURE]BROADCASTING consumer's consume detail is empty
Posted by GitBox <gi...@apache.org>.
RongtongJin commented on issue #3316:
URL: https://github.com/apache/rocketmq/issues/3316#issuecomment-912893024
This is because the broadcast mode offset store is managed locally. If there is a better solution, you can submit a pull request.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq] coder-zzzz commented on issue #3316: [NEW FEATURE]BROADCASTING consumer's consume detail is empty
Posted by GitBox <gi...@apache.org>.
coder-zzzz commented on issue #3316:
URL: https://github.com/apache/rocketmq/issues/3316#issuecomment-913282739
If we can update offset to broker under broadcast mode, the offset store in broker only used by admin cli?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq] veimguo commented on issue #3316: [NEW FEATURE]BROADCASTING consumer's consume detail is empty
Posted by GitBox <gi...@apache.org>.
veimguo commented on issue #3316:
URL: https://github.com/apache/rocketmq/issues/3316#issuecomment-1001498042
> maybe you can have a try on other solution: using different cluster consumer ids under cluster model instead of broadcast...
so, under what situation, shoud we use broadcasting，it seems that broadcast model has certain flaws.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq] lizhimins commented on issue #3316: [NEW FEATURE]BROADCASTING consumer's consume detail is empty
Posted by GitBox <gi...@apache.org>.
lizhimins commented on issue #3316:
URL: https://github.com/apache/rocketmq/issues/3316#issuecomment-914199884
When client restarts, it will use a different client ID. Offset may not be well managed.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq] coder-zzzz commented on issue #3316: [NEW FEATURE]BROADCASTING consumer's consume detail is empty
Posted by GitBox <gi...@apache.org>.
coder-zzzz commented on issue #3316:
URL: https://github.com/apache/rocketmq/issues/3316#issuecomment-914202618
> When client restarts, it will use a different client ID. Offset may not be well managed.
how about use the client's ip to identify every client?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org