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/06/27 08:39:46 UTC
[GitHub] [rocketmq] yanglifan opened a new issue #2123: To support the versioned message routing
yanglifan opened a new issue #2123:
URL: https://github.com/apache/rocketmq/issues/2123
In the test environment, messages of one topic may have different versions. And consumers of this topic are same too, also have different versions. And the message should be send to the consumer which has the same version.
**e.g., the message v1 of the topic A should be send to the consumer v1 if it existed in some of consumer groups, or any consumer can process the versioned message if there is no versioned consumer of some consumer groups.**
We already has an internal mechanism to support this requirement based on the message selection/allocation, but I hope to have a discussion to create a common solve this issue.
----------------------------------------------------------------
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 #2123: To support the versioned message routing
Posted by GitBox <gi...@apache.org>.
lizhiboo commented on issue #2123:
URL: https://github.com/apache/rocketmq/issues/2123#issuecomment-650747973
> @lizhiboo currently RMQ producer's and consumer's routing mechanism are both based on the client side extension (`MessageQueueSelector`/`AllocateMessageQueueStrategy`). So the versioned message routing can be also implemented in the same way. But the downside is that producers and consumers have to be configured in the same approach, so routing in the broker side may be a good choice to support the feature like the versioned message routing.
I agree with u, moving rebalance mechanism to broker is a good choice. Client will be light.
----------------------------------------------------------------
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] yanglifan commented on issue #2123: To support the versioned message routing
Posted by GitBox <gi...@apache.org>.
yanglifan commented on issue #2123:
URL: https://github.com/apache/rocketmq/issues/2123#issuecomment-650724092
@lizhiboo currently RMQ producer's and consumer's routing mechanism are both based on the client side extension (`MessageQueueSelector`/`AllocateMessageQueueStrategy`). So the versioned message routing can be also implemented in the same way. But the downside is that producers and consumers have to be configured in the same approach, so routing in the broker side may be a good choice to support the feature like the versioned message routing.
----------------------------------------------------------------
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 #2123: To support the versioned message routing
Posted by GitBox <gi...@apache.org>.
lizhiboo commented on issue #2123:
URL: https://github.com/apache/rocketmq/issues/2123#issuecomment-650664014
IMO, implements this feature would modify producer's route and consumer's rebalance mechanism. Consumer holds a partition by rebalance. Let versioned consumer consume the corresponding versioned message, producer will produce versioned message to specific versioned partition. Besides, consumer should hold its specific versioned partition.
----------------------------------------------------------------
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