[ 
https://issues.apache.org/jira/browse/FLUME-1893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13652695#comment-13652695
 ] 

Hudson commented on FLUME-1893:
-------------------------------

Integrated in flume-trunk #407 (See 
[https://builds.apache.org/job/flume-trunk/407/])
    FLUME-1893. File Channel could miss possible checkpoint corruption. 
(Revision 7a6e3db005dfc7848eeb62b6e66b91dc00a7f726)

     Result = FAILURE
mpercy : 
http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=7a6e3db005dfc7848eeb62b6e66b91dc00a7f726
Files : 
* 
flume-ng-channels/flume-file-channel/src/test/java/org/apache/flume/channel/file/TestFileChannelRestart.java
* 
flume-ng-channels/flume-file-channel/src/main/java/org/apache/flume/channel/file/EventQueueBackingStoreFile.java
* 
flume-ng-channels/flume-file-channel/src/main/java/org/apache/flume/channel/file/FileChannel.java
* 
flume-ng-channels/flume-file-channel/src/main/java/org/apache/flume/channel/file/Log.java

                
> File Channel could miss possible checkpoint corruption
> ------------------------------------------------------
>
>                 Key: FLUME-1893
>                 URL: https://issues.apache.org/jira/browse/FLUME-1893
>             Project: Flume
>          Issue Type: Bug
>    Affects Versions: v1.3.1
>            Reporter: Hari Shreedharan
>            Assignee: Hari Shreedharan
>             Fix For: v1.4.0
>
>         Attachments: FLUME-1893.patch
>
>
> If the first 4 bytes of the checkpoint are overwritten, then the current 
> sanity check will miss it because we read the first long and then cast it to 
> an int, missing the first 4 bytes when we check the version. First 4 bytes 
> being corrupt could indicate further corruption in the checkpoint which 
> cannot be verified because the remaining data consists mostly of pointers to 
> files, which if not used are simply ignored by the replay mechanism

--
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

Reply via email to