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/01/25 07:01:37 UTC
[GitHub] superheizai opened a new issue #718: updateTopicPerm need to check
all related brokers config
superheizai opened a new issue #718: updateTopicPerm need to check all related brokers config
URL: https://github.com/apache/rocketmq/issues/718
**BUG REPORT**
1. Please describe the issue you observed:
updateTopicPerm on a broker in a cluster with 2 brokers. The first step is to update topic perm to 2, it succeed. Then update it to 6, failed.
Because I have 2 brokers, when update one of them to 2, the 2 brokers perm will be 2&6. The implementation will take only the first one's perm to check if it can be updated.
TopicRouteData topicRouteData = defaultMQAdminExt.examineTopicRouteInfo(topic);
assert topicRouteData != null;
List<QueueData> queueDatas = topicRouteData.getQueueDatas();
assert queueDatas != null && queueDatas.size() > 0;
QueueData queueData = queueDatas.get(0);
2. Please tell us about your environment:
3. Other information (e.g. detailed explanation, logs, related issues, suggestions how to fix, etc):
**FEATURE REQUEST**
1. Please describe the feature you are requesting.
2. Provide any additional detail on your proposed use case for this feature.
2. Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?
4. If there are some sub-tasks using -[] for each subtask and create a corresponding issue to map to the sub task:
- [sub-task1-issue-number](example_sub_issue1_link_here): sub-task1 description here,
- [sub-task2-issue-number](example_sub_issue2_link_here): sub-task2 description here,
- ...
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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
Re:[GitHub] superheizai opened a new issue #718: updateTopicPerm
need to check all related brokers config
Posted by 罗成刚 <ar...@163.com>.
+1
At 2019-01-25 15:01:37, "GitBox" <gi...@apache.org> wrote:
>superheizai opened a new issue #718: updateTopicPerm need to check all related brokers config
>URL: https://github.com/apache/rocketmq/issues/718
>
>
>
> **BUG REPORT**
>
> 1. Please describe the issue you observed:
>
> updateTopicPerm on a broker in a cluster with 2 brokers. The first step is to update topic perm to 2, it succeed. Then update it to 6, failed.
>
> Because I have 2 brokers, when update one of them to 2, the 2 brokers perm will be 2&6. The implementation will take only the first one's perm to check if it can be updated.
>
> TopicRouteData topicRouteData = defaultMQAdminExt.examineTopicRouteInfo(topic);
> assert topicRouteData != null;
> List<QueueData> queueDatas = topicRouteData.getQueueDatas();
> assert queueDatas != null && queueDatas.size() > 0;
> QueueData queueData = queueDatas.get(0);
>
>
> 2. Please tell us about your environment:
>
> 3. Other information (e.g. detailed explanation, logs, related issues, suggestions how to fix, etc):
>
> **FEATURE REQUEST**
>
> 1. Please describe the feature you are requesting.
>
> 2. Provide any additional detail on your proposed use case for this feature.
>
> 2. Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?
>
> 4. If there are some sub-tasks using -[] for each subtask and create a corresponding issue to map to the sub task:
>
> - [sub-task1-issue-number](example_sub_issue1_link_here): sub-task1 description here,
> - [sub-task2-issue-number](example_sub_issue2_link_here): sub-task2 description here,
> - ...
>
>
>----------------------------------------------------------------
>This is an automated message from the Apache Git Service.
>To respond to the message, please log on 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