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/08/12 02:00:33 UTC
[GitHub] [rocketmq] 88888-IT opened a new issue #3250: RocketMq is currently designed to have one or more consumequeues for each topic. Why not one or more consumequeues for each topic and tag
88888-IT opened a new issue #3250:
URL: https://github.com/apache/rocketmq/issues/3250
RocketMq is currently designed to have one or more consumequeues for each topic. Why not one or more consumequeues for each topic and tag
--
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] 88888-IT commented on issue #3250: RocketMq is currently designed to have one or more consumequeues for each topic. Why not one or more consumequeues for each topic and tag
Posted by GitBox <gi...@apache.org>.
88888-IT commented on issue #3250:
URL: https://github.com/apache/rocketmq/issues/3250#issuecomment-897408116
> why you need distinguish consumer queue by tag? It is topic dimension right now.
If the consumer subscribes to the tag under the topic, the consumer needs to traverse the queue and compare the tagHashCode to fetch the item
--
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] ni-ze commented on issue #3250: RocketMq is currently designed to have one or more consumequeues for each topic. Why not one or more consumequeues for each topic and tag
Posted by GitBox <gi...@apache.org>.
ni-ze commented on issue #3250:
URL: https://github.com/apache/rocketmq/issues/3250#issuecomment-897381697
why you need distinguish consumer queue by tag? It is topic dimension right now.
--
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] francisoliverlee commented on issue #3250: RocketMq is currently designed to have one or more consumequeues for each topic. Why not one or more consumequeues for each topic and tag
Posted by GitBox <gi...@apache.org>.
francisoliverlee commented on issue #3250:
URL: https://github.com/apache/rocketmq/issues/3250#issuecomment-897795234
interesting idea and how do you want to do this ?
--
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] caigy commented on issue #3250: RocketMq is currently designed to have one or more consumequeues for each topic. Why not one or more consumequeues for each topic and tag
Posted by GitBox <gi...@apache.org>.
caigy commented on issue #3250:
URL: https://github.com/apache/rocketmq/issues/3250#issuecomment-919671261
If there're many tags, will performance be affected by the great number of queue files?
--
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] ni-ze commented on issue #3250: RocketMq is currently designed to have one or more consumequeues for each topic. Why not one or more consumequeues for each topic and tag
Posted by GitBox <gi...@apache.org>.
ni-ze commented on issue #3250:
URL: https://github.com/apache/rocketmq/issues/3250#issuecomment-897299435
tag is decided by use, broker can not control how many tags users use. if we design consume queues by tag, that is a disaster for broker stability.
--
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] Git-Yang commented on issue #3250: RocketMq is currently designed to have one or more consumequeues for each topic. Why not one or more consumequeues for each topic and tag
Posted by GitBox <gi...@apache.org>.
Git-Yang commented on issue #3250:
URL: https://github.com/apache/rocketmq/issues/3250#issuecomment-979680071
> > tag is decided by user, broker can not control how many tags users use. if we design consume queues by tag, that is a disaster for broker stability.
>
> What if the user defines the tag and creates it in the broker
Maybe you can write the required ‘topic+tag’ to a separate topic based on business needs.
--
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] 88888-IT commented on issue #3250: RocketMq is currently designed to have one or more consumequeues for each topic. Why not one or more consumequeues for each topic and tag
Posted by GitBox <gi...@apache.org>.
88888-IT commented on issue #3250:
URL: https://github.com/apache/rocketmq/issues/3250#issuecomment-898095819
> interesting idea and how do you want to do this ?
If the producer registers the topic and tag with the broker before sending messages, the broker can create four queues for the topic and tag. Is it possible to load balance a queue when a producer sends a message and then send the message to it? I don't know if that's feasible
--
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] caigy commented on issue #3250: RocketMq is currently designed to have one or more consumequeues for each topic. Why not one or more consumequeues for each topic and tag
Posted by GitBox <gi...@apache.org>.
caigy commented on issue #3250:
URL: https://github.com/apache/rocketmq/issues/3250#issuecomment-919670381
@88888-IT Do you mean 'grouping' queues by subscription relationship? You can provide more detailed design so that more people can join the discussion.
--
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] ni-ze commented on issue #3250: RocketMq is currently designed to have one or more consumequeues for each topic. Why not one or more consumequeues for each topic and tag
Posted by GitBox <gi...@apache.org>.
ni-ze commented on issue #3250:
URL: https://github.com/apache/rocketmq/issues/3250#issuecomment-897372515
> > tag is decided by user, broker can not control how many tags users use. if we design consume queues by tag, that is a disaster for broker stability.
>
> What if the user defines the tag and creates it in the broker
You can not do that. Tag is define by user when send a message in producer.
--
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] ni-ze edited a comment on issue #3250: RocketMq is currently designed to have one or more consumequeues for each topic. Why not one or more consumequeues for each topic and tag
Posted by GitBox <gi...@apache.org>.
ni-ze edited a comment on issue #3250:
URL: https://github.com/apache/rocketmq/issues/3250#issuecomment-897299435
tag is decided by user, broker can not control how many tags users use. if we design consume queues by tag, that is a disaster for broker stability.
--
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] 88888-IT commented on issue #3250: RocketMq is currently designed to have one or more consumequeues for each topic. Why not one or more consumequeues for each topic and tag
Posted by GitBox <gi...@apache.org>.
88888-IT commented on issue #3250:
URL: https://github.com/apache/rocketmq/issues/3250#issuecomment-897375677
> What if the user defines the tag and creates it in the broker
> You can not do that. Tag is define by user when send a message in producer.
我的意思是如果生产者提前在broker中创建好tag再去使用，这个时候是不是就可以根据tag来区分consumequeue
--
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] 88888-IT commented on issue #3250: RocketMq is currently designed to have one or more consumequeues for each topic. Why not one or more consumequeues for each topic and tag
Posted by GitBox <gi...@apache.org>.
88888-IT commented on issue #3250:
URL: https://github.com/apache/rocketmq/issues/3250#issuecomment-897303372
> tag is decided by user, broker can not control how many tags users use. if we design consume queues by tag, that is a disaster for broker stability.
What if the user defines the tag and creates it in the broker
--
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