[
https://issues.apache.org/jira/browse/ROCKETMQ-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15813555#comment-15813555
]
Kailai Shao commented on ROCKETMQ-36:
-------------------------------------
It's quite a valuable point! Using RAM disk makes broker more real-time while
pointing to somewhere else makes logs persistent.
I wonder whether it is better to provide a default configuration and offer
ability for user to modify using input arguments meanwhile?
> Improve broker's GC logs storing
> --------------------------------
>
> Key: ROCKETMQ-36
> URL: https://issues.apache.org/jira/browse/ROCKETMQ-36
> Project: Apache RocketMQ
> Issue Type: Improvement
> Reporter: Roman Shtykh
> Assignee: vongosling
>
> To avoid disk I/O potential competition between GC and broker threads, GC
> logs are placed into {{/dev/shm}}. This is a valid concern, but I propose
> more consideration to be done to situations when the system crashes (and, as
> a result, in-memory logs disappear).
> Long-term logging is essential for analysis of the brokers' performance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
