[GitHub] superheizai commented on issue #835: examineConsumeStats for DefaultMQAdminExtImpl will onley check master

[GitBox <gi...@apache.org>]

superheizai commented on issue #835: examineConsumeStats for DefaultMQAdminExtImpl will onley check master
URL: https://github.com/apache/rocketmq/issues/835#issuecomment-466434935
 
 
   > I checked the current implementation:
   > 
   > 1. If the master is alive, consume offset will always commit to master broker. ConsumerProgress command queries offset from the master.
   > 2. If the master is down, consume offset will commit to the slave broker with minimum id. In this situation, consumerProgress command will pick a random slave to query offset. We should do some optimize in this case.
   > 
   > So, if you are the first case, check whether offset commit failed or other problems. If you are in the second case, it's the problem of the current implementation.
   
   Another condition for case 1 is I have enabled slave. When read for messages for days ago, master will give suggestion broker id for client to pull from. Client PullAPIWrapper will check suggestion brokerId for each pull. And  PullMessageProcessor will commit offset.
   It seems different with your description? Would you please help to check  again?

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