[ https://issues.apache.org/jira/browse/FLUME-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roshan Naik updated FLUME-2068: ------------------------------- Attachment: FLUME-1.3.1-2068.patch renaming patch file to have flume version so its not confusing > File Channel issue - recovering from BadCheckpoint exception on Windows > ----------------------------------------------------------------------- > > Key: FLUME-2068 > URL: https://issues.apache.org/jira/browse/FLUME-2068 > Project: Flume > Issue Type: Bug > Components: Channel, File Channel, Windows > Affects Versions: v1.3.1 > Reporter: Roshan Naik > Assignee: Roshan Naik > Attachments: FLUME-1.3.1-2068.patch > > > In EventQueueBackingStoreFileV3 constructor, if it detects that the > checkpoint and meta files have differing logWriteOrderIds, it throws a > BadCheckpointException. Controls goes back to the exception handler in > Log.replay() which attempts to delete all the files in checkpoint directory > and start fresh. The same file names are reused when starting fresh. > Unfortunately this does not work on Windows since the deletion of the > checkpoint file in the checkpointDir fails. The failure is due to the fact > that the checkpoint file is memory mapped. Unless it is unmapped the deletion > will not succeed... and unfortunately Java does not have unmap support. > Windows does not permit deletion (or renaming) of files in use. -- 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