[
https://issues.apache.org/jira/browse/FLUME-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003657#comment-14003657
]
Edward Sargisson commented on FLUME-2385:
-----------------------------------------
I agree that this is highly annoying - especially so that you have to know to
look back to just when the spamming started to determine what the failure
actually was.
However, I also think it's important that administrators know that the source
has stopped. I would probably support simply logging a message saying,
"Spooling Directory Source <name> has stopped. Refer to the start of these
messages to determine why."
We could consider logging this only every 5s or similar but that's a bit more
interesting to implement.
> 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
> Priority: Minor
>
> 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.2#6252)
