[
https://issues.apache.org/jira/browse/FLUME-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13631970#comment-13631970
]
Paul Chavez edited comment on FLUME-1993 at 4/15/13 6:19 PM:
-------------------------------------------------------------
Attached alternate fix. Instead of explicitly closing the file, don't create
the new instance unless we deleted the old one. Also, check for file existence
before attempting delete when getting next instance to appease Windows.
Note: tried to follow the instructions for creating a code review, but the
review web app would not let me attach the patch "The selected file does not
appear to be a diff."
was (Author: paulchavez):
Attached alternate fix. Instead of explicitly closing the file, don't
create the new instance unless we deleted the old one. Also, check for file
existence before attempting delete when getting next instance to appease
Windows.
> On Windows, when using the spooling directory source, there is a file sharing
> violation when trying to delete tracker file
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: FLUME-1993
> URL: https://issues.apache.org/jira/browse/FLUME-1993
> Project: Flume
> Issue Type: Bug
> Components: Sinks+Sources
> Affects Versions: v1.4.0
> Reporter: Phil Scala
> Attachments: FLUME-1993.patch, ReliableSpoolingFileEventReader.java,
> ReliableSpoolingFileEventReader.java.patch
>
>
> spooling directory source
> org.apache.flume.client.avro.ReliableSpoolingFileEventReader.getNextFile()
> Gets an instance of a DurablePositionTracker and is not calling close() on it
> before then creating another instance... thus not calling close on the
> underlying DataFileWriter. This left the file locked in Windows and hence
> any delete attempts were failing...causing the Agent to spin around and
> around trying to delete this file and creating endless numbers of the
> temporary tracker files.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
