[jira] [Resolved] (FLUME-631) Log rotation overwrites old logs on service stop

["Ashish Paliwal (JIRA)" <ji...@apache.org>]

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

Ashish Paliwal resolved FLUME-631.
----------------------------------
       Resolution: Won't Fix
    Fix Version/s: v0.9.5

Won't fix. 0.X branch not maintained anymore

> Log rotation overwrites old logs on service stop
> ------------------------------------------------
>
>                 Key: FLUME-631
>                 URL: https://issues.apache.org/jira/browse/FLUME-631
>             Project: Flume
>          Issue Type: Bug
>          Components: Node
>    Affects Versions: v0.9.3
>            Reporter: Disabled imported user
>            Priority: Minor
>             Fix For: v0.9.5
>
>
> It seems that when stopping the flume-node service the log file is automatically rotated. Occasionally this will result in another log file getting overwritten, possibly corresponding to the date when the service was started. Notice:
> # head flume-flume-node-....log.2011-05-16
> 2011-05-17 00:00:00,665 INFO com.cloudera.flume.handlers.endtoend.AckChecksumChecker
> In this case, I believe the service was started on 5/16. I lost that original log file, so I cannot confirm this :-)
> My temp workaround is to gzip logfiles after they have been automatically rotated, via a cronjob. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)