[
https://issues.apache.org/jira/browse/FLUME-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13446551#comment-13446551
]
Hudson commented on FLUME-1527:
-------------------------------
Integrated in flume-1.3.0 #5 (See
[https://builds.apache.org/job/flume-1.3.0/5/])
FLUME-1527. Seed TransactionID/WriteOrderID in the case no logs need to be
replayed. (Revision 52f67c2dad6598faced14dba4c98bfae7b291714)
Result = FAILURE
hshreedharan :
http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git;a=summary&a=commit&h=52f67c2dad6598faced14dba4c98bfae7b291714
Files :
*
flume-ng-channels/flume-file-channel/src/main/java/org/apache/flume/channel/file/ReplayHandler.java
> Seed TransactionID/WriteOrderID in the case no logs need to be replayed
> -----------------------------------------------------------------------
>
> Key: FLUME-1527
> URL: https://issues.apache.org/jira/browse/FLUME-1527
> Project: Flume
> Issue Type: Bug
> Components: Channel
> Reporter: Brock Noland
> Assignee: Brock Noland
> Attachments: FLUME-1527-0.patch
>
>
> At startup we seed the sequence numbers for transaction id and write order id
> with the highest of the following:
> -current time in ms
> -the highest id we find from the log files we find during replay
> There is a small and unlikely hole in this logic. If an agent had received
> tons of events and thus the sequence numbers had incremented past current
> time in ms, then checkpointed, received no more events, and restarted. We
> would not have any logs to replay and as such would seed the sequence numbers
> with only current time in ms.
--
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
