SpoolDir issue

[manish jaiswal <ma...@gmail.com>]

How to deal with this issue in production.
If a file is written to after being placed into the spooling directory,
Flume will print an error to its log file and stop processing
If a file name is reused at a later time, Flume will print an error to its
log file and stop processing.

Please help.

Re: SpoolDir issue

[iain wright <ia...@gmail.com>]

Hi Manish,

This is expected behavior of the spooling directory source:
https://flume.apache.org/FlumeUserGuide.html#spooling-directory-source

You will need to have the files flushed/completed elsewhere, and moved into
the spooling directory with a unique name.

-- 
Iain Wright

This email message is confidential, intended only for the recipient(s)
named above and may contain information that is privileged, exempt from
disclosure under applicable law. If you are not the intended recipient, do
not disclose or disseminate the message to anyone except the intended
recipient. If you have received this message in error, or are not the named
recipient(s), please immediately notify the sender by return email, and
delete all copies of this message.

On Mon, Aug 8, 2016 at 12:27 PM, manish jaiswal <ma...@gmail.com>
wrote:

> How to deal with this issue in production.
> If a file is written to after being placed into the spooling directory,
> Flume will print an error to its log file and stop processing
> If a file name is reused at a later time, Flume will print an error to its
> log file and stop processing.
>
> Please help.
>