[
https://issues.apache.org/jira/browse/FLUME-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13165178#comment-13165178
]
Ossi L commented on FLUME-631:
------------------------------
This has happened to us several times already.
Here are the results of last stop:
root@server6:/var/log/flume >ls -tlr flume-flume-node-server6.*
-rw-r--r-- 1 flume flume 0 Nov 29 13:16 flume-flume-node-server6.out.1
-rw-r--r-- 1 flume flume 119585306 Nov 30 23:59
flume-flume-node-server6.log.2011-11-30
-rw-r--r-- 1 flume flume 115278301 Dec 1 23:59
flume-flume-node-server6.log.2011-12-01
-rw-r--r-- 1 flume flume 103790508 Dec 2 23:59
flume-flume-node-server6.log.2011-12-02
-rw-r--r-- 1 flume flume 103812829 Dec 3 23:59
flume-flume-node-server6.log.2011-12-03
-rw-r--r-- 1 flume flume 103825331 Dec 4 23:59
flume-flume-node-server6.log.2011-12-04
-rw-r--r-- 1 flume flume 89876674 Dec 5 23:59
flume-flume-node-server6.log.2011-12-05
-rw-r--r-- 1 flume flume 87966045 Dec 6 23:59
flume-flume-node-server6.log.2011-12-06
-rw-r--r-- 1 flume flume 144808152 Dec 7 23:59
flume-flume-node-server6.log.2011-12-07
-rw-r--r-- 1 flume flume 46734953 Dec 8 13:11
flume-flume-node-server6.log.2011-11-29
-rw-r--r-- 1 flume flume 0 Dec 8 13:11 flume-flume-node-server6.out
-rw-r--r-- 1 flume flume 59998 Dec 8 13:12 flume-flume-node-server6.log
please note timestamp of file flume-flume-node-server6.log.2011-11-29.
And first 2 lines:
root@server6:/var/log/flume >head -2 flume-flume-node-server6.log.2011-11-29
2011-12-08 00:00:00,031 INFO
com.cloudera.flume.handlers.hdfs.EscapedCustomDfsSink: Opening
hdfs://namenode:8020/flume/aa/httpd-fe/2011-12-08/server2-access-20111207-235935253+0100.4793280510405625.00353777
2011-12-08 00:00:00,118 INFO com.cloudera.flume.handlers.hdfs.CustomDfsSink:
Creating HDFS file:
hdfs://namenode:8020/flume/aa/httpd-fe/2011-12-08/server2-access-20111207-235935253+0100.4793280510405625.00353777.tmp
which should be:
root@server6:/var/log/flume >head -2
2011-12-08_and_older/flume-flume-node-server6.log.2011-11-29
2011-11-29 13:16:59,133 INFO com.cloudera.flume.watchdog.FlumeWatchdog: Dropped
a pidfile='/var/run/flume/flume-flume-node.pid' with pid=25846
2011-11-29 13:16:59,166 INFO com.cloudera.flume.conf.FlumeConfiguration:
Loading configurations from conf
> 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
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
