You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
rocketmq5.2当消息消费者向从服务器拉取消息后,会一直从从服务器拉取?
1)如果从服务器的slaveReadEnable设置为false,则下次拉取,从主服务器拉取。
2)如果从服务器允许读取并且从服务器积压的消息未超过其物理内存的40%,下次拉取使用的Broker为订阅组的brokerId指定的Broker服务器,该值默认为0,代表主服务器。
3)如果从服务器允许读取并且从服务器积压的消息超过了其物理内存的40%,下次拉取使用的Broker为订阅组的whichBrokerWhenConsumeSlowly指定的Broker服务器,该值默认为1。
当我不是采用普通的M-S架构,使用的controller来管理的M-S,controller分配的slave的BrokerId可能>1,whichBrokerWhenConsumeSlowly默认的是1,第3)点的whichBrokerWhenConsumeSlowly是如何选择的呢?是只能从brokerid=1的从服务器拉取消息,还是whichBrokerWhenConsumeSlowly=1代表的是从服务器,不管其BrokerId是多少?
Beta Was this translation helpful? Give feedback.
All reactions