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/02/03 01:39:44 UTC

[GitHub] [rocketmq] wangyanan0629 opened a new issue #2653: RocketMQ messages are sent to two nodes in the cluster. What is the reason that the consumer can only consume data on one node? 中文：rocketmq消息发送到集群的两个节点,消费者只能消费一个节点上的数据是什么原因？

wangyanan0629 opened a new issue #2653:
URL: https://github.com/apache/rocketmq/issues/2653


   ![image](https://user-images.githubusercontent.com/67535305/106684768-0d0f3400-6602-11eb-8b73-e529bc6dafb4.png)
   ![image](https://user-images.githubusercontent.com/67535305/106684804-22845e00-6602-11eb-83b3-ef44acd7d7d1.png)
   ![image](https://user-images.githubusercontent.com/67535305/106684844-3334d400-6602-11eb-8260-cfe83a83dd0c.png)
   
   Why can messages on Broker2 be distributed to Broker2 and not consumed by subscribing？
   --------------------------------------------------------------
   为什么broker2上的消息可以分发到上边而不能被订阅消费？


----------------------------------------------------------------
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] wangyanan0629 removed a comment on issue #2653: RocketMQ messages are sent to two nodes in the cluster. What is the reason that the consumer can only consume data on one node?

Posted by GitBox <gi...@apache.org>.
wangyanan0629 removed a comment on issue #2653:
URL: https://github.com/apache/rocketmq/issues/2653#issuecomment-781248098


   > > > > 只有在广播模式的时候可以连上broker2,集群模式的时候只能消费broker1上的消息
   > > > 
   > > > 
   > > > 消费者只启动了单台吗？是以容器的方式启动的吗？
   > > 
   > > 
   > > 用的是docker容器启动的集群
   > 
   > 是同一台机器上有多个docker容器吗？是不是instanceName相同导致的，可以consumer强制setInstanceName，保证每一个consumer的instanceName都独一无二试试
   这个是docker-compose的配置
   `version: '3.5'
   services:
     namesrv1:
       image: rocketmqinc/rocketmq:4.3.0
       container_name: namesrv1
       ports:
         - 9876:9876
       volumes:
         - /opt/rocketmq/namesrv1/log:/opt/logs
         - /opt/rocketmq/namesrv1/data:/opt/store
       command: sh mqnamesrv
       networks:
         rocketmq:
           aliases:
             - namesrv1
     namesrv2:
       image: rocketmqinc/rocketmq:4.3.0
       container_name: namesrv2
       ports:
         - 9877:9876
       volumes:
         - /opt/rocketmq/namesrv2/log:/opt/logs
         - /opt/rocketmq/namesrv2/data:/opt/store
       command: sh mqnamesrv
       networks:
         rocketmq:
           aliases:
             - namesrv2
     broker-m-1:
       image: rocketmqinc/rocketmq:4.3.0
       container_name: broker-m-1
       links:
         - namesrv1:namesrv1
         - namesrv2:namesrv2
       ports:
         - 10909:10909
         - 10911:10911
         - 10912:10912
       environment:
         TZ: Asia/Shanghai
         NAMESRV_ADDR: "namesrv1:9876"
         JAVA_OPTS: "-Duser.home=/opt"
         JAVA_OPT_EXT: "-server -Xms256m -Xmx256m -Xmn256m"
       volumes:
         - /opt/rocketmq/broker-m-1/log:/opt/logs
         - /opt/rocketmq/broker-m-1/data:/opt/store
         - /opt/rocketmq/broker-m-1/conf/broker-m-1.conf:/opt/rocketmq-4.3.0/conf/broker-m-1.conf
       command: sh mqbroker -c /opt/rocketmq-4.3.0/conf/broker-m-1.conf autoCreateTopicEnable=true &
       networks:
         rocketmq:
           aliases:
             - broker-m-1
     broker-s-1:
       image: rocketmqinc/rocketmq:4.3.0
       container_name: broker-s-1
       links:
         - namesrv1:namesrv1
         - namesrv2:namesrv2
       ports:
         - 11909:10909
         - 11911:11911
         - 11912:10912
       environment:
         TZ: Asia/Shanghai
         NAMESRV_ADDR: "namesrv1:9876"
         JAVA_OPTS: "-Duser.home=/opt"
         JAVA_OPT_EXT: "-server -Xms256m -Xmx256m -Xmn256m"
       volumes:
         - /opt/rocketmq/broker-s-1/log:/opt/logs
         - /opt/rocketmq/broker-s-1/data:/opt/store
         - /opt/rocketmq/broker-s-1/conf/broker-s-1.conf:/opt/rocketmq-4.3.0/conf/broker-s-1.conf
       command: sh mqbroker -c /opt/rocketmq-4.3.0/conf/broker-s-1.conf autoCreateTopicEnable=true &
       networks:
         rocketmq:
           aliases:
             - broker-s-1
     broker-m-2:
       image: rocketmqinc/rocketmq:4.3.0
       container_name: broker-m-2
       links:
         - namesrv1:namesrv1
         - namesrv2:namesrv1
       ports:
         - 12909:10909
         - 12911:12911
         - 12912:10912
       environment:
         TZ: Asia/Shanghai
         NAMESRV_ADDR: "namesrv1:9876"
         JAVA_OPTS: "-Duser.home=/opt"
         JAVA_OPT_EXT: "-server -Xms256m -Xmx256m -Xmn256m"
       volumes:
         - /opt/rocketmq/broker-m-2/log:/opt/logs
         - /opt/rocketmq/broker-m-2/data:/opt/store
         - /opt/rocketmq/broker-m-2/conf/broker-m-2.conf:/opt/rocketmq-4.3.0/conf/broker-m-2.conf
       command: sh mqbroker -c /opt/rocketmq-4.3.0/conf/broker-m-2.conf autoCreateTopicEnable=true &
       networks:
         rocketmq:
           aliases:
             - broker-m-2
     broker-s-2:
       image: rocketmqinc/rocketmq:4.3.0
       container_name: broker-s-2
       links:
         - namesrv1:namesrv1
         - namesrv2:namesrv2
       ports:
         - 13909:10909
         - 13911:13911
         - 13912:10912
       environment:
         TZ: Asia/Shanghai
         NAMESRV_ADDR: "namesrv1:9876"
         JAVA_OPTS: "-Duser.home=/opt"
         JAVA_OPT_EXT: "-server -Xms256m -Xmx256m -Xmn256m"
       volumes:
         - /opt/rocketmq/broker-s-2/log:/opt/logs
         - /opt/rocketmq/broker-s-2/data:/opt/store
         - /opt/rocketmq/broker-s-2/conf/broker-s-2.conf:/opt/rocketmq-4.3.0/conf/broker-s-2.conf
       command: sh mqbroker -c /opt/rocketmq-4.3.0/conf/broker-s-2.conf autoCreateTopicEnable=true &
       networks:
         rocketmq:
           aliases:
             - broker-s-2
     rocketmq-console:
       image: styletang/rocketmq-console-ng
       container_name: rocketmq-console
       ports:
         - 8090:8080
       environment:
         JAVA_OPTS: -Drocketmq.namesrv.addr=namesrv1:9876;namesrv2:9877 -Dcom.rocketmq.sendMessageWithVIPChannel=false
       networks:
         rocketmq:
           aliases:
             - rocketmq-console
   networks:
     rocketmq:
       name: rocketmq
       driver: bridge`


----------------------------------------------------------------
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] lizhimins commented on issue #2653: RocketMQ messages are sent to two nodes in the cluster. What is the reason that the consumer can only consume data on one node? 中文：rocketmq消息发送到集群的两个节点,消费者只能消费一个节点上的数据是什么原因？

Posted by GitBox <gi...@apache.org>.
lizhimins commented on issue #2653:
URL: https://github.com/apache/rocketmq/issues/2653#issuecomment-773888590


   从第二个截图来看 确实发送到两台broker上了，可以排查下消费者是否能连到 broker2 上


----------------------------------------------------------------
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] wangyanan0629 commented on issue #2653: RocketMQ messages are sent to two nodes in the cluster. What is the reason that the consumer can only consume data on one node?

Posted by GitBox <gi...@apache.org>.
wangyanan0629 commented on issue #2653:
URL: https://github.com/apache/rocketmq/issues/2653#issuecomment-781252119


   > > instanceName
   > 
   > > > > > 只有在广播模式的时候可以连上broker2,集群模式的时候只能消费broker1上的消息
   > > > > 
   > > > > 
   > > > > 消费者只启动了单台吗？是以容器的方式启动的吗？
   > > > 
   > > > 
   > > > 用的是docker容器启动的集群
   > > 
   > > 
   > > 是同一台机器上有多个docker容器吗？是不是instanceName相同导致的，可以consumer强制setInstanceName，保证每一个consumer的instanceName都独一无二试试
   > 
   > 是通过docker-compose搭建的单机集群，集群架构是2nameServer+2master+2salve
   这个是docker-compose的配置文件
   [docker-compose.txt](https://github.com/apache/rocketmq/files/6002156/docker-compose.txt)


----------------------------------------------------------------
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] wangyanan0629 commented on issue #2653: RocketMQ messages are sent to two nodes in the cluster. What is the reason that the consumer can only consume data on one node?

Posted by GitBox <gi...@apache.org>.
wangyanan0629 commented on issue #2653:
URL: https://github.com/apache/rocketmq/issues/2653#issuecomment-781248098


   > > > > 只有在广播模式的时候可以连上broker2,集群模式的时候只能消费broker1上的消息
   > > > 
   > > > 
   > > > 消费者只启动了单台吗？是以容器的方式启动的吗？
   > > 
   > > 
   > > 用的是docker容器启动的集群
   > 
   > 是同一台机器上有多个docker容器吗？是不是instanceName相同导致的，可以consumer强制setInstanceName，保证每一个consumer的instanceName都独一无二试试
   这个是docker-compose的配置
   `version: '3.5'
   services:
     namesrv1:
       image: rocketmqinc/rocketmq:4.3.0
       container_name: namesrv1
       ports:
         - 9876:9876
       volumes:
         - /opt/rocketmq/namesrv1/log:/opt/logs
         - /opt/rocketmq/namesrv1/data:/opt/store
       command: sh mqnamesrv
       networks:
         rocketmq:
           aliases:
             - namesrv1
     namesrv2:
       image: rocketmqinc/rocketmq:4.3.0
       container_name: namesrv2
       ports:
         - 9877:9876
       volumes:
         - /opt/rocketmq/namesrv2/log:/opt/logs
         - /opt/rocketmq/namesrv2/data:/opt/store
       command: sh mqnamesrv
       networks:
         rocketmq:
           aliases:
             - namesrv2
     broker-m-1:
       image: rocketmqinc/rocketmq:4.3.0
       container_name: broker-m-1
       links:
         - namesrv1:namesrv1
         - namesrv2:namesrv2
       ports:
         - 10909:10909
         - 10911:10911
         - 10912:10912
       environment:
         TZ: Asia/Shanghai
         NAMESRV_ADDR: "namesrv1:9876"
         JAVA_OPTS: "-Duser.home=/opt"
         JAVA_OPT_EXT: "-server -Xms256m -Xmx256m -Xmn256m"
       volumes:
         - /opt/rocketmq/broker-m-1/log:/opt/logs
         - /opt/rocketmq/broker-m-1/data:/opt/store
         - /opt/rocketmq/broker-m-1/conf/broker-m-1.conf:/opt/rocketmq-4.3.0/conf/broker-m-1.conf
       command: sh mqbroker -c /opt/rocketmq-4.3.0/conf/broker-m-1.conf autoCreateTopicEnable=true &
       networks:
         rocketmq:
           aliases:
             - broker-m-1
     broker-s-1:
       image: rocketmqinc/rocketmq:4.3.0
       container_name: broker-s-1
       links:
         - namesrv1:namesrv1
         - namesrv2:namesrv2
       ports:
         - 11909:10909
         - 11911:11911
         - 11912:10912
       environment:
         TZ: Asia/Shanghai
         NAMESRV_ADDR: "namesrv1:9876"
         JAVA_OPTS: "-Duser.home=/opt"
         JAVA_OPT_EXT: "-server -Xms256m -Xmx256m -Xmn256m"
       volumes:
         - /opt/rocketmq/broker-s-1/log:/opt/logs
         - /opt/rocketmq/broker-s-1/data:/opt/store
         - /opt/rocketmq/broker-s-1/conf/broker-s-1.conf:/opt/rocketmq-4.3.0/conf/broker-s-1.conf
       command: sh mqbroker -c /opt/rocketmq-4.3.0/conf/broker-s-1.conf autoCreateTopicEnable=true &
       networks:
         rocketmq:
           aliases:
             - broker-s-1
     broker-m-2:
       image: rocketmqinc/rocketmq:4.3.0
       container_name: broker-m-2
       links:
         - namesrv1:namesrv1
         - namesrv2:namesrv1
       ports:
         - 12909:10909
         - 12911:12911
         - 12912:10912
       environment:
         TZ: Asia/Shanghai
         NAMESRV_ADDR: "namesrv1:9876"
         JAVA_OPTS: "-Duser.home=/opt"
         JAVA_OPT_EXT: "-server -Xms256m -Xmx256m -Xmn256m"
       volumes:
         - /opt/rocketmq/broker-m-2/log:/opt/logs
         - /opt/rocketmq/broker-m-2/data:/opt/store
         - /opt/rocketmq/broker-m-2/conf/broker-m-2.conf:/opt/rocketmq-4.3.0/conf/broker-m-2.conf
       command: sh mqbroker -c /opt/rocketmq-4.3.0/conf/broker-m-2.conf autoCreateTopicEnable=true &
       networks:
         rocketmq:
           aliases:
             - broker-m-2
     broker-s-2:
       image: rocketmqinc/rocketmq:4.3.0
       container_name: broker-s-2
       links:
         - namesrv1:namesrv1
         - namesrv2:namesrv2
       ports:
         - 13909:10909
         - 13911:13911
         - 13912:10912
       environment:
         TZ: Asia/Shanghai
         NAMESRV_ADDR: "namesrv1:9876"
         JAVA_OPTS: "-Duser.home=/opt"
         JAVA_OPT_EXT: "-server -Xms256m -Xmx256m -Xmn256m"
       volumes:
         - /opt/rocketmq/broker-s-2/log:/opt/logs
         - /opt/rocketmq/broker-s-2/data:/opt/store
         - /opt/rocketmq/broker-s-2/conf/broker-s-2.conf:/opt/rocketmq-4.3.0/conf/broker-s-2.conf
       command: sh mqbroker -c /opt/rocketmq-4.3.0/conf/broker-s-2.conf autoCreateTopicEnable=true &
       networks:
         rocketmq:
           aliases:
             - broker-s-2
     rocketmq-console:
       image: styletang/rocketmq-console-ng
       container_name: rocketmq-console
       ports:
         - 8090:8080
       environment:
         JAVA_OPTS: -Drocketmq.namesrv.addr=namesrv1:9876;namesrv2:9877 -Dcom.rocketmq.sendMessageWithVIPChannel=false
       networks:
         rocketmq:
           aliases:
             - rocketmq-console
   networks:
     rocketmq:
       name: rocketmq
       driver: bridge`


----------------------------------------------------------------
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] dujinsong removed a comment on issue #2653: RocketMQ messages are sent to two nodes in the cluster. What is the reason that the consumer can only consume data on one node?

Posted by GitBox <gi...@apache.org>.
dujinsong removed a comment on issue #2653:
URL: https://github.com/apache/rocketmq/issues/2653#issuecomment-1035930601


   > > > > instanceName
   > > > 
   > > > 
   > > > > > > > 只有在广播模式的时候可以连上broker2,集群模式的时候只能消费broker1上的消息
   > > > > > > 
   > > > > > > 
   > > > > > > 消费者只启动了单台吗？是以容器的方式启动的吗？
   > > > > > 
   > > > > > 
   > > > > > 用的是docker容器启动的集群
   > > > > 
   > > > > 
   > > > > 是同一台机器上有多个docker容器吗？是不是instanceName相同导致的，可以consumer强制setInstanceName，保证每一个consumer的instanceName都独一无二试试
   > > > 
   > > > 
   > > > 是通过docker-compose搭建的单机集群，集群架构是2nameServer+2master+2salve
   > > > 这个是docker-compose的配置文件
   > > > [docker-compose.txt](https://github.com/apache/rocketmq/files/6002156/docker-compose.txt)
   > 
   > 设置强制消费也测试过，不起作用
   
   哈喽，我遇到过此情况，不知道能否解决你的问题。先启动一个broker集群，正常收发消息，后面扩容了一个broker集群，扩容的集群能发送消息，但是没有消费，我通过console将topic以及哈喽，我遇到过此情况，不知道能否解决你的问题。先启动一个broker集群，正常收发消息，后面扩容了一个broker集群，扩容的集群能发送消息，但是没有消费，我通过console将topic以及消费组添加到新集群中后能够消费消息。扩容broker集群提前将plain_acl.yml、topics.json 以及subscriptionGroup.json文件拷贝到新集群的相应目录下能够避免此问题。消费组添加到新集群中后能够消费消息。扩容broker集群提前将plain_acl.yml、topics.json 以及subscriptionGroup.json文件拷贝到新集群的相应目录下能够避免此问题。


-- 
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] RongtongJin commented on issue #2653: RocketMQ messages are sent to two nodes in the cluster. What is the reason that the consumer can only consume data on one node?

Posted by GitBox <gi...@apache.org>.
RongtongJin commented on issue #2653:
URL: https://github.com/apache/rocketmq/issues/2653#issuecomment-781209994


   > > > 只有在广播模式的时候可以连上broker2,集群模式的时候只能消费broker1上的消息
   > > 
   > > 
   > > 消费者只启动了单台吗？是以容器的方式启动的吗？
   > 
   > 用的是docker容器启动的集群
   
   是同一台机器上有多个docker容器吗？是不是instanceName相同导致的，可以consumer强制setInstanceName，保证每一个consumer的instanceName都独一无二试试


----------------------------------------------------------------
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] dujinsong commented on issue #2653: RocketMQ messages are sent to two nodes in the cluster. What is the reason that the consumer can only consume data on one node?

Posted by GitBox <gi...@apache.org>.
dujinsong commented on issue #2653:
URL: https://github.com/apache/rocketmq/issues/2653#issuecomment-1035931746


   > > > > instanceName
   > > > 
   > > > 
   > > > > > > > 只有在广播模式的时候可以连上broker2,集群模式的时候只能消费broker1上的消息
   > > > > > > 
   > > > > > > 
   > > > > > > 消费者只启动了单台吗？是以容器的方式启动的吗？
   > > > > > 
   > > > > > 
   > > > > > 用的是docker容器启动的集群
   > > > > 
   > > > > 
   > > > > 是同一台机器上有多个docker容器吗？是不是instanceName相同导致的，可以consumer强制setInstanceName，保证每一个consumer的instanceName都独一无二试试
   > > > 
   > > > 
   > > > 是通过docker-compose搭建的单机集群，集群架构是2nameServer+2master+2salve
   > > > 这个是docker-compose的配置文件
   > > > [docker-compose.txt](https://github.com/apache/rocketmq/files/6002156/docker-compose.txt)
   > 
   > 设置强制消费也测试过，不起作用
   
   哈喽，我遇到过此情况，不知道能否解决你的问题。先启动一个broker集群，正常收发消息，后面扩容了一个broker集群，扩容的集群能发送消息，但是没有消费，我通过console将topic以及消费组添加到新集群中后能够消费消息。扩容broker集群提前将plain_acl.yml、topics.json 以及subscriptionGroup.json文件拷贝到新集群的相应目录下能够避免此问题。


-- 
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] wangyanan0629 commented on issue #2653: RocketMQ messages are sent to two nodes in the cluster. What is the reason that the consumer can only consume data on one node?

Posted by GitBox <gi...@apache.org>.
wangyanan0629 commented on issue #2653:
URL: https://github.com/apache/rocketmq/issues/2653#issuecomment-781070560


   > > 只有在广播模式的时候可以连上broker2,集群模式的时候只能消费broker1上的消息
   > 
   > 消费者只启动了单台吗？是以容器的方式启动的吗？
   
   用的是docker容器启动的集群


----------------------------------------------------------------
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] RongtongJin commented on issue #2653: RocketMQ messages are sent to two nodes in the cluster. What is the reason that the consumer can only consume data on one node?

Posted by GitBox <gi...@apache.org>.
RongtongJin commented on issue #2653:
URL: https://github.com/apache/rocketmq/issues/2653#issuecomment-778773592


   
   > 只有在广播模式的时候可以连上broker2,集群模式的时候只能消费broker1上的消息
   
   消费者只启动了单台吗？是以容器的方式启动的吗？
   


----------------------------------------------------------------
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] dujinsong commented on issue #2653: RocketMQ messages are sent to two nodes in the cluster. What is the reason that the consumer can only consume data on one node?

Posted by GitBox <gi...@apache.org>.
dujinsong commented on issue #2653:
URL: https://github.com/apache/rocketmq/issues/2653#issuecomment-1035930601


   > > > > instanceName
   > > > 
   > > > 
   > > > > > > > 只有在广播模式的时候可以连上broker2,集群模式的时候只能消费broker1上的消息
   > > > > > > 
   > > > > > > 
   > > > > > > 消费者只启动了单台吗？是以容器的方式启动的吗？
   > > > > > 
   > > > > > 
   > > > > > 用的是docker容器启动的集群
   > > > > 
   > > > > 
   > > > > 是同一台机器上有多个docker容器吗？是不是instanceName相同导致的，可以consumer强制setInstanceName，保证每一个consumer的instanceName都独一无二试试
   > > > 
   > > > 
   > > > 是通过docker-compose搭建的单机集群，集群架构是2nameServer+2master+2salve
   > > > 这个是docker-compose的配置文件
   > > > [docker-compose.txt](https://github.com/apache/rocketmq/files/6002156/docker-compose.txt)
   > 
   > 设置强制消费也测试过，不起作用
   
   哈喽，我遇到过此情况，不知道能否解决你的问题。先启动一个broker集群，正常收发消息，后面扩容了一个broker集群，扩容的集群能发送消息，但是没有消费，我通过console将topic以及哈喽，我遇到过此情况，不知道能否解决你的问题。先启动一个broker集群，正常收发消息，后面扩容了一个broker集群，扩容的集群能发送消息，但是没有消费，我通过console将topic以及消费组添加到新集群中后能够消费消息。扩容broker集群提前将plain_acl.yml、topics.json 以及subscriptionGroup.json文件拷贝到新集群的相应目录下能够避免此问题。消费组添加到新集群中后能够消费消息。扩容broker集群提前将plain_acl.yml、topics.json 以及subscriptionGroup.json文件拷贝到新集群的相应目录下能够避免此问题。


-- 
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] dujinsong commented on issue #2653: RocketMQ messages are sent to two nodes in the cluster. What is the reason that the consumer can only consume data on one node?

Posted by GitBox <gi...@apache.org>.
dujinsong commented on issue #2653:
URL: https://github.com/apache/rocketmq/issues/2653#issuecomment-1035931222


   > > > > instanceName
   > > > 
   > > > 
   > > > > > > > 只有在广播模式的时候可以连上broker2,集群模式的时候只能消费broker1上的消息
   > > > > > > 
   > > > > > > 
   > > > > > > 消费者只启动了单台吗？是以容器的方式启动的吗？
   > > > > > 
   > > > > > 
   > > > > > 用的是docker容器启动的集群
   > > > > 
   > > > > 
   > > > > 是同一台机器上有多个docker容器吗？是不是instanceName相同导致的，可以consumer强制setInstanceName，保证每一个consumer的instanceName都独一无二试试
   > > > 
   > > > 
   > > > 是通过docker-compose搭建的单机集群，集群架构是2nameServer+2master+2salve
   > > > 这个是docker-compose的配置文件
   > > > [docker-compose.txt](https://github.com/apache/rocketmq/files/6002156/docker-compose.txt)
   > 
   > 设置强制消费也测试过，不起作用
   
   哈喽，我遇到过此情况，不知道能否解决你的问题。先启动一个broker集群，正常收发消息，后面扩容了一个broker集群，扩容的集群能发送消息，但是没有消费，我通过console将topic以及消费组添加到新集群中后能够消费消息。扩容broker集群提前将plain_acl.yml、topics.json 以及subscriptionGroup.json文件拷贝到新集群的相应目录下能够避免此问题。消费组添加到新集群中后能够消费消息。扩容broker集群提前将plain_acl.yml、topics.json 以及subscriptionGroup.json文件拷贝到新集群的相应目录下能够避免此问题。


-- 
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] wangyanan0629 commented on issue #2653: RocketMQ messages are sent to two nodes in the cluster. What is the reason that the consumer can only consume data on one node?

Posted by GitBox <gi...@apache.org>.
wangyanan0629 commented on issue #2653:
URL: https://github.com/apache/rocketmq/issues/2653#issuecomment-781243775


   > instanceName
   
   
   
   > > > > 只有在广播模式的时候可以连上broker2,集群模式的时候只能消费broker1上的消息
   > > > 
   > > > 
   > > > 消费者只启动了单台吗？是以容器的方式启动的吗？
   > > 
   > > 
   > > 用的是docker容器启动的集群
   > 
   > 是同一台机器上有多个docker容器吗？是不是instanceName相同导致的，可以consumer强制setInstanceName，保证每一个consumer的instanceName都独一无二试试
   
   是通过docker-compose搭建的单机集群，集群架构是2nameServer+2master+2salve


----------------------------------------------------------------
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] wangyanan0629 commented on issue #2653: RocketMQ messages are sent to two nodes in the cluster. What is the reason that the consumer can only consume data on one node? 中文：rocketmq消息发送到集群的两个节点,消费者只能消费一个节点上的数据是什么原因？

Posted by GitBox <gi...@apache.org>.
wangyanan0629 commented on issue #2653:
URL: https://github.com/apache/rocketmq/issues/2653#issuecomment-773890590


   只有在广播模式的时候可以连上broker2,集群模式的时候只能消费broker1上的消息


----------------------------------------------------------------
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] wangyanan0629 commented on issue #2653: RocketMQ messages are sent to two nodes in the cluster. What is the reason that the consumer can only consume data on one node?

Posted by GitBox <gi...@apache.org>.
wangyanan0629 commented on issue #2653:
URL: https://github.com/apache/rocketmq/issues/2653#issuecomment-781750847


   > > > instanceName
   > > 
   > > 
   > > > > > > 只有在广播模式的时候可以连上broker2,集群模式的时候只能消费broker1上的消息
   > > > > > 
   > > > > > 
   > > > > > 消费者只启动了单台吗？是以容器的方式启动的吗？
   > > > > 
   > > > > 
   > > > > 用的是docker容器启动的集群
   > > > 
   > > > 
   > > > 是同一台机器上有多个docker容器吗？是不是instanceName相同导致的，可以consumer强制setInstanceName，保证每一个consumer的instanceName都独一无二试试
   > > 
   > > 
   > > 是通过docker-compose搭建的单机集群，集群架构是2nameServer+2master+2salve
   > > 这个是docker-compose的配置文件
   > > [docker-compose.txt](https://github.com/apache/rocketmq/files/6002156/docker-compose.txt)
   
   设置强制消费也测试过，不起作用


----------------------------------------------------------------
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] lizhimins commented on issue #2653: RocketMQ messages are sent to two nodes in the cluster. What is the reason that the consumer can only consume data on one node? 中文：rocketmq消息发送到集群的两个节点,消费者只能消费一个节点上的数据是什么原因？

Posted by GitBox <gi...@apache.org>.
lizhimins commented on issue #2653:
URL: https://github.com/apache/rocketmq/issues/2653#issuecomment-773888590


   从第二个截图来看 确实发送到两台broker上了，可以排查下消费者是否能连到 broker2 上


----------------------------------------------------------------
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] wangyanan0629 commented on issue #2653: RocketMQ messages are sent to two nodes in the cluster. What is the reason that the consumer can only consume data on one node? 中文：rocketmq消息发送到集群的两个节点,消费者只能消费一个节点上的数据是什么原因？

Posted by GitBox <gi...@apache.org>.
wangyanan0629 commented on issue #2653:
URL: https://github.com/apache/rocketmq/issues/2653#issuecomment-773890590


   只有在广播模式的时候可以连上broker2,集群模式的时候只能消费broker1上的消息


----------------------------------------------------------------
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] dujinsong removed a comment on issue #2653: RocketMQ messages are sent to two nodes in the cluster. What is the reason that the consumer can only consume data on one node?

Posted by GitBox <gi...@apache.org>.
dujinsong removed a comment on issue #2653:
URL: https://github.com/apache/rocketmq/issues/2653#issuecomment-1035931222


   > > > > instanceName
   > > > 
   > > > 
   > > > > > > > 只有在广播模式的时候可以连上broker2,集群模式的时候只能消费broker1上的消息
   > > > > > > 
   > > > > > > 
   > > > > > > 消费者只启动了单台吗？是以容器的方式启动的吗？
   > > > > > 
   > > > > > 
   > > > > > 用的是docker容器启动的集群
   > > > > 
   > > > > 
   > > > > 是同一台机器上有多个docker容器吗？是不是instanceName相同导致的，可以consumer强制setInstanceName，保证每一个consumer的instanceName都独一无二试试
   > > > 
   > > > 
   > > > 是通过docker-compose搭建的单机集群，集群架构是2nameServer+2master+2salve
   > > > 这个是docker-compose的配置文件
   > > > [docker-compose.txt](https://github.com/apache/rocketmq/files/6002156/docker-compose.txt)
   > 
   > 设置强制消费也测试过，不起作用
   
   哈喽，我遇到过此情况，不知道能否解决你的问题。先启动一个broker集群，正常收发消息，后面扩容了一个broker集群，扩容的集群能发送消息，但是没有消费，我通过console将topic以及消费组添加到新集群中后能够消费消息。扩容broker集群提前将plain_acl.yml、topics.json 以及subscriptionGroup.json文件拷贝到新集群的相应目录下能够避免此问题。消费组添加到新集群中后能够消费消息。扩容broker集群提前将plain_acl.yml、topics.json 以及subscriptionGroup.json文件拷贝到新集群的相应目录下能够避免此问题。


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