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 2020/05/28 15:29:13 UTC
[GitHub] [rocketmq] lebron374 opened a new issue #2052: any good practice to deal with multi test environment in RocketMq
lebron374 opened a new issue #2052:
URL: https://github.com/apache/rocketmq/issues/2052
in our company，use rocketMq to process message，but sometimes we need message only consume in particular server。
we modify the consume rebalance policy to let one server to consume all messages。
but i want know any best practice in community？
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq] vongosling closed issue #2052: any good practice to deal with multi test environment in RocketMq
Posted by GitBox <gi...@apache.org>.
vongosling closed issue #2052:
URL: https://github.com/apache/rocketmq/issues/2052
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq] Jaskey commented on issue #2052: any good practice to deal with multi test environment in RocketMq
Posted by GitBox <gi...@apache.org>.
Jaskey commented on issue #2052:
URL: https://github.com/apache/rocketmq/issues/2052#issuecomment-642519008
1.The most convenient way would be: set up different rocketmq broker cluster with separate name server cluster for different test env
2.Another way could be use the same cluster , but set up a env flag to your topic, while your consumer or producer start to work, always use the topic of that test env.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq] Jaskey edited a comment on issue #2052: any good practice to deal with multi test environment in RocketMq
Posted by GitBox <gi...@apache.org>.
Jaskey edited a comment on issue #2052:
URL: https://github.com/apache/rocketmq/issues/2052#issuecomment-642519008
1.The most convenient way would be: set up different rocketmq broker cluster with separate name server cluster for different test env
2.Another way could be using the same cluster , but set up a env flag to your topic, while your consumer or producer start to work, always use the topic of that test env.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq] lizhiboo commented on issue #2052: any good practice to deal with multi test environment in RocketMq
Posted by GitBox <gi...@apache.org>.
lizhiboo commented on issue #2052:
URL: https://github.com/apache/rocketmq/issues/2052#issuecomment-635699533
> in our company，use rocketMq to process message，but sometimes we need message only consume in particular server。
>
> we modify the consume rebalance policy to let one server to consume all messages。
> but i want know any best practice in community？
Try to use the following method, business layer make sure only the particular server start consume task by using a lock.
` consumer.setMessageModel(MessageModel.BROADCASTING);
`
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org