baihezhuo opened a new issue #1585: [TIMEOUT_CLEAN_QUEUE]
URL: https://github.com/apache/rocketmq/issues/1585
 
 
   1. Hardware configuration
       8C - 32G - ESSD200G
   
   2. The configuration for broker:
   ```
   brokerClusterName=
   brokerName=
   brokerId=0
   namesrvAddr=
   listenPort=10911
   fileReservedTime=48
   diskMaxUsedSpaceRatio=95
   storePathRootDir=/usr/local/rocketmq/store
   storePathCommitLog=/usr/local/rocketmq/store/commitlog
   storePathConsumerQueue=/usr/local/rocketmq/consumequeue
   **brokerRole=SYNC_MASTER**
   **flushDiskType=ASYNC_FLUSH**
   **sendMessageThreadPoolNums=64**
   **useReentrantLockWhenPutMessage=true**
   ```
   
   3. Problem phenomenon:
   - A lot of flow control log information often occurs,By tracking the code, 
it is found that the synchronous replication between the master node and the 
slave node has timed out:
   do sync transfer other node, wait return, but failed, topic
   putMessage not in lock eclipse time(ms)=6194
   
   - log error 1
   - org.apache.rocketmq.client.exception.MQBrokerException: CODE: 2  DESC: 
[TIMEOUT_CLEAN_QUEUE]broker busy, start flow control for a while, period in 
queue: 209ms, size of queue: 56
   - log error 2
   - 2019-11-09 15:46:08 ERROR SendMessageThread_26 - do sync transfer other 
node, wait return, but failed, topic: FUND_PENDING_CLEARING_MESSAGE_TOPIC tags: 
null client address: 10.32.0.157
   2019-11-09 15:46:08 WARN SendMessageThread_26 - putMessage not in lock 
eclipse time(ms)=6194, bodyLength=2062
   2019-11-09 15:46:08 ERROR SendMessageThread_57 - do sync transfer other 
node, wait return, but failed, topic: FUND_PENDING_CLEARING_MESSAGE_TOPIC tags: 
null client address: 10.32.0.157
   2019-11-09 15:46:08 WARN SendMessageThread_57 - putMessage not in lock 
eclipse time(ms)=6194, bodyLength=2056
   
   4. How to troubleshoot and solve such problems?
   
   
   
   

----------------------------------------------------------------
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:
[email protected]


With regards,
Apache Git Services

Reply via email to