[
https://issues.apache.org/jira/browse/ROCKETMQ-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15803527#comment-15803527
]
ASF GitHub Bot commented on ROCKETMQ-31:
----------------------------------------
Github user shroman commented on the issue:
https://github.com/apache/incubator-rocketmq/pull/29
yes, I see, you want to reduce disk I/O by placing the file into `/dev/shm`.
Well, GC logging has a minimal overhead. And to get a high-performance
broker, I would tune my JVM to get smaller GC pauses, which has much larger
impact on the overall performance.
Also, is it ok not to persist your GC logs? Long-term logging is essential
for analysis of the brokers' performance.
> 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)
