[
https://issues.apache.org/jira/browse/ROCKETMQ-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15803371#comment-15803371
]
ASF GitHub Bot commented on ROCKETMQ-31:
----------------------------------------
Github user iskl commented on the issue:
https://github.com/apache/incubator-rocketmq/pull/29
Dear @shroman , thanks for your suggestion :)
In my concept, broker thread is **time sensitive**. When broker thread in a
MQ broker is in I/O operation and GC occurs, an **I/O competition** appears
between broker thread and GC thread. It may bring **long time latency to broker
thread**.
Linux distributions based on the 2.6 kernel and later offer `/dev/shm` as
shared memory in the form of a **RAM disk**
[(link)](https://en.wikipedia.org/wiki/Shared_memory). Pointing GC log to
`/dev/shm` can avoid I/O competition between broker thread and GC thread.
In conclusion, I tend to use `-Xloggc:/dev/shm/mq_gc_%p.log` :)
> Deletion needed for `$HOME/rmq_bk_gc.log` in `bin/mqbroker`
> -----------------------------------------------------------
>
> Key: ROCKETMQ-31
> URL: https://issues.apache.org/jira/browse/ROCKETMQ-31
> Project: Apache RocketMQ
> Issue Type: Bug
> Reporter: Kailai Shao
> Assignee: vongosling
>
> Going through "Quick Start" manual, I got warning message when I start
> {{bin/mqbroker}} as below:
> {code}
> cp: /Users/kailai/rmq_bk_gc.log: No such file or directory
> {code}
> The error is caused by the following code in {{bin/mqbroker}}:
> {code}
> rm -f $HOME/rmq_bk_gc.log.bac
> cp $HOME/rmq_bk_gc.log $HOME/rmq_bk_gc.log.bac
> {code}
> Since the GC log has been set to {{/dev/shm/mq_gc_%p.log}} due to
> {{bin/runbroker.sh}} Line 41, the operation for {{$HOME/rmq_bk_gc.log}} in
> {{bin/mqbroker}} should be deleted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
