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

Posted to dev@tubemq.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/05/19 05:03:00 UTC

[jira] [Updated] (TUBEMQ-128) Shorten the log clearup check cycle

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

ASF GitHub Bot updated TUBEMQ-128:
----------------------------------
    Labels: performance pull-request-available  (was: performance)

> Shorten the log clearup check cycle
> -----------------------------------
>
>                 Key: TUBEMQ-128
>                 URL: https://issues.apache.org/jira/browse/TUBEMQ-128
>             Project: Apache TubeMQ
>          Issue Type: Improvement
>            Reporter: Guocheng Zhang
>            Priority: Major
>              Labels: performance, pull-request-available
>             Fix For: 0.5.0
>
>         Attachments: image-2020-05-19-04-54-57-533.png
>
>
> At present, the default value of logClearupDurationMs for  log clearup detection period is 30 minutes:
>  !image-2020-05-19-04-54-57-533.png! 
> In the case of relatively large throughput, file cleaning will not be timely, resulting in file disk full condition. 30 minutes is adjusted to 3 minutes, the minimum allowable value is adjusted to 1 minutes



--
This message was sent by Atlassian Jira
(v8.3.4#803005)