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 2018/07/09 02:26:36 UTC
[GitHub] lizhanhui commented on issue #348: [TIMEOUT_CLEAN_QUEUE]broker busy
lizhanhui commented on issue #348: [TIMEOUT_CLEAN_QUEUE]broker busy
URL: https://github.com/apache/rocketmq/issues/348#issuecomment-403342028
The short answer is: In your broker configuration file, configure this entry: waitTimeMillsInSendQueue to a larger value to override the default one: 200.
Long answer:
When configured as synchronous disk IO flush, it takes time to sync data of a small batch of messages to disk before writing responses to message sender. Those unprocessed requests are buffered in a queue. To ensure broker won't suspend producer excessive long period of time, it will expire sending requests if they are not processed within `waitTimeMillsInSendQueue`, which may block application too long in case synchronous sending API is employed. This strategy, in general, is called __fail-early, fail-fast__.
The default value is tuned for asynchrous disk flushing. In case synchronous disk flushing is used, you'd better __measure and tune__.
----------------------------------------------------------------
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