[
https://issues.apache.org/jira/browse/FLUME-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14206103#comment-14206103
]
Hudson commented on FLUME-2385:
-------------------------------
UNSTABLE: Integrated in flume-trunk #692 (See
[https://builds.apache.org/job/flume-trunk/692/])
FLUME-2385. Remove incorrect log message at INFO level in Spool Directory
Source. (hshreedharan:
http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=2c18533253be786b9c60bf687cdf38d2384d2625)
* flume-ng-core/src/main/java/org/apache/flume/source/SpoolDirectorySource.java
> Flume spans log file with "Spooling Directory Source runner has shutdown"
> messages at INFO level
> ------------------------------------------------------------------------------------------------
>
> Key: FLUME-2385
> URL: https://issues.apache.org/jira/browse/FLUME-2385
> Project: Flume
> Issue Type: Improvement
> Affects Versions: v1.4.0
> Reporter: Justin Hayes
> Assignee: Phil Scala
> Priority: Minor
> Fix For: v1.6.0
>
> Attachments: FLUME-2385-0.patch
>
>
> When I start an agent with the following config, the spooling directory
> source emits "14/05/14 22:36:12 INFO source.SpoolDirectorySource: Spooling
> Directory Source runner has shutdown." messages twice a second. Pretty
> innocuous but it will fill up the file system needlessly and get in the way
> of other INFO messages.
> cis.sources = httpd
> cis.sinks = loggerSink
> cis.channels = mem2logger
> cis.sources.httpd.type = spooldir
> cis.sources.httpd.spoolDir = /var/log/httpd
> cis.sources.httpd.trackerDir = /var/lib/flume-ng/tracker/httpd
> cis.sources.httpd.channels = mem2logger
> cis.sinks.loggerSink.type = logger
> cis.sinks.loggerSink.channel = mem2logger
> cis.channels.mem2logger.type = memory
> cis.channels.mem2logger.capacity = 10000
> cis.channels.mem2logger.transactionCapacity = 1000
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
