You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@rocketmq.apache.org by "dongeforever (JIRA)" <ji...@apache.org> on 2017/05/25 06:29:04 UTC

[jira] [Closed] (ROCKETMQ-36) Improve broker's GC logs storing

     [ https://issues.apache.org/jira/browse/ROCKETMQ-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

dongeforever closed ROCKETMQ-36.
--------------------------------
    Resolution: Fixed

solved with PR: https://github.com/apache/incubator-rocketmq/pull/87

> 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: Roman Shtykh
>             Fix For: 4.1.0-incubating
>
>
> 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.15#6346)