[
https://issues.apache.org/jira/browse/FLUME-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14559548#comment-14559548
]
Phil Scala commented on FLUME-2704:
-----------------------------------
Thanks Somin, the idea seems reasonable to me, but just could you elaborate on
the issue you were seeing that this fixes. Where I am going is: while 500ms is
fast for checking for new files, if you were seeing race conditions where the
file was still being writen to when this timer realized there was a new file
then you could still have this issue, just not as frequently. We may need to
focus on how the file was placed into the spool directory.
> Configurable poll delay for spooling directory source
> -----------------------------------------------------
>
> Key: FLUME-2704
> URL: https://issues.apache.org/jira/browse/FLUME-2704
> Project: Flume
> Issue Type: Improvement
> Components: Sinks+Sources
> Affects Versions: v1.5.2, 1.6
> Reporter: Somin Mithraa
> Priority: Minor
> Labels: SpoolDir, pollDelay, sources
> Attachments: FLUME-2704.patch
>
>
> SpoolDir source polls a directory for new files at specific interval. This
> interval(or poll delay) is currently hardcoded as 500ms.
> 500ms may be too fast for some applications. This JIRA is to make this
> property configurable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
