- Please describe the issue you observed:
-
What did you do (The steps to reproduce)?
let consumer run
-
What did you expect to see?
keep consuming messages
-
What did you see instead?
stopped consuming messages
- Please tell us about your environment:
-
What is your OS?
CentOS Linux 7.6.1810
-
What is your client version?
commit hash: b29bf5b
commited at 2020.03.23
-
What is your RocketMQ version?
V4_3_0
- Other information (e.g. detailed explanation, logs, related issues, suggestions on how to fix, etc):
rocketmq log:
2020-Mar-28 08:42:42.124297:unlock success of mq:MessageQueue [topic=browser, brokerName=broker-1, queueId=1][unlock:335]
2020-Mar-28 08:42:42.124426:PullRequest for [MessageQueue [topic=browser, brokerName=broker-1, queueId=2]] has been expired 9111 ms,m_lastPullTimestamp = 1585356033013 ms[isPullRequestExpired:211]
2020-Mar-28 08:42:42.124486:Drop mq:MessageQueue [topic=browser, brokerName=broker-1, queueId=2] according Pull timeout.[updateRequestTableInRebalance:501]
2020-Mar-28 08:42:42.124554:oneway updateConsumeOffsetToBroker of mq:MessageQueue [topic=browser, brokerName=broker-1, queueId=2], its offset is:268305037[updateConsumeOffsetToBroker:310]
日志一直循环出现上述内容。
只出现在跨机房消费的场景(ping延迟40ms左右),网络可能会有波动但从未断开。每次消费者启动后可以正常运行一段时间(几个小时或者几天),但在某个时间点突然不再消费新消息,导致该消费者所分配到的队列堆积,也不会再分配给其他正常消费者。超时设置(try lock timeout & connect timeout)均使用默认值。
共部署4-6个消费者,任意一个消费者均多次出现过上述情况,必须重启消费者才能恢复。
What did you do (The steps to reproduce)?
let consumer run
What did you expect to see?
keep consuming messages
What did you see instead?
stopped consuming messages
What is your OS?
CentOS Linux 7.6.1810
What is your client version?
commit hash: b29bf5b
commited at 2020.03.23
What is your RocketMQ version?
V4_3_0
rocketmq log:
2020-Mar-28 08:42:42.124297:unlock success of mq:MessageQueue [topic=browser, brokerName=broker-1, queueId=1][unlock:335]
2020-Mar-28 08:42:42.124426:PullRequest for [MessageQueue [topic=browser, brokerName=broker-1, queueId=2]] has been expired 9111 ms,m_lastPullTimestamp = 1585356033013 ms[isPullRequestExpired:211]
2020-Mar-28 08:42:42.124486:Drop mq:MessageQueue [topic=browser, brokerName=broker-1, queueId=2] according Pull timeout.[updateRequestTableInRebalance:501]
2020-Mar-28 08:42:42.124554:oneway updateConsumeOffsetToBroker of mq:MessageQueue [topic=browser, brokerName=broker-1, queueId=2], its offset is:268305037[updateConsumeOffsetToBroker:310]
日志一直循环出现上述内容。
只出现在跨机房消费的场景(ping延迟40ms左右),网络可能会有波动但从未断开。每次消费者启动后可以正常运行一段时间(几个小时或者几天),但在某个时间点突然不再消费新消息,导致该消费者所分配到的队列堆积,也不会再分配给其他正常消费者。超时设置(try lock timeout & connect timeout)均使用默认值。
共部署4-6个消费者,任意一个消费者均多次出现过上述情况,必须重启消费者才能恢复。