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 2019/11/10 09:04:02 UTC

[GitHub] [rocketmq] MountainOne commented on issue #1497: Not reset queueId in MQClientAPIImpl#onExceptionImpl()

MountainOne commented on issue #1497: Not reset queueId in MQClientAPIImpl#onExceptionImpl()
URL: https://github.com/apache/rocketmq/issues/1497#issuecomment-552176230
 
 
   When creating a topic in RocketMQ, call `createTopic(String key, String newTopic, int queueNum, int topicSysFlag)` to create the topic. The third parameter of this method is the specified number of message queues. For example, `queueNum=4`, then 4 read queues and 4 write queues will be created in the specified broker, and the number of queues created for this topic will be the same in all brokers. So there won't be a problem that different brokers with different queue counts under the same topic, so there is no need to reset `queueId` when asynchronous call fails.
   
   在 RocketMQ 创建 topic 的时候,调用`createTopic(String key, String newTopic, int queueNum, int topicSysFlag)`创建topic。这个方法的第三个参数为指定的消息队列数。比如`queueNum=4`,那么就会在指定的 broker 中创建 4 个读队列和 4 个写队列,所有的 broker 中针对该主题创建的队列数都是一样的。所以不会出现同一主题下,不同的 broker 具有不同的队列数的问题,因此也不需要在异步发送失败的时候重新设置`queueId`。

----------------------------------------------------------------
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


With regards,
Apache Git Services