You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Brock Noland (JIRA)" <ji...@apache.org> on 2012/08/30 23:14:07 UTC
[jira] [Created] (FLUME-1527) Seed TransactionID/WriteOrderID in
the case no logs need to be replayed
Brock Noland created FLUME-1527:
-----------------------------------
Summary: 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
At startup with see 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
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 see 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
[jira] [Commented] (FLUME-1527) Seed TransactionID/WriteOrderID in
the case no logs need to be replayed
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13446560#comment-13446560 ]
Hudson commented on FLUME-1527:
-------------------------------
Integrated in flume-trunk #291 (See [https://builds.apache.org/job/flume-trunk/291/])
FLUME-1527. Seed TransactionID/WriteOrderID in the case no logs need to be replayed. (Revision 63e0f43c5281a643af5709d4b09c15d03c142c77)
Result = SUCCESS
hshreedharan : http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git;a=summary&a=commit&h=63e0f43c5281a643af5709d4b09c15d03c142c77
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
[jira] [Updated] (FLUME-1527) Seed TransactionID/WriteOrderID in
the case no logs need to be replayed
Posted by "Brock Noland (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brock Noland updated FLUME-1527:
--------------------------------
Description:
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
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 see the sequence numbers with only current time in ms.
was:
At startup se 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
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 see the sequence numbers with only current time in ms.
> 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
>
> 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
> 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 see 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
[jira] [Updated] (FLUME-1527) Seed TransactionID/WriteOrderID in
the case no logs need to be replayed
Posted by "Brock Noland (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brock Noland updated FLUME-1527:
--------------------------------
Description:
At startup se 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
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 see the sequence numbers with only current time in ms.
was:
At startup with see 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
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 see the sequence numbers with only current time in ms.
> 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
>
> At startup se 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
> 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 see 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
[jira] [Reopened] (FLUME-1527) Seed TransactionID/WriteOrderID in
the case no logs need to be replayed
Posted by "Brock Noland (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brock Noland reopened FLUME-1527:
---------------------------------
This same change should be made to ReplayHandler.replayLogv1. I think it's even more unlikely in that case, but still should be done.
> 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
[jira] [Resolved] (FLUME-1527) Seed TransactionID/WriteOrderID in
the case no logs need to be replayed
Posted by "Hari Shreedharan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hari Shreedharan resolved FLUME-1527.
-------------------------------------
Resolution: Fixed
Assignee: Brock Noland
Patch committed, rev: 63e0f43c5281a643af5709d4b09c15d03c142c77. Thanks Brock!
> 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
[jira] [Updated] (FLUME-1527) Seed TransactionID/WriteOrderID in
the case no logs need to be replayed
Posted by "Brock Noland (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brock Noland updated FLUME-1527:
--------------------------------
Attachment: FLUME-1527-0.patch
patch from rb
> 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
> 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
[jira] [Commented] (FLUME-1527) Seed TransactionID/WriteOrderID in
the case no logs need to be replayed
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (FLUME-1527) Seed TransactionID/WriteOrderID in
the case no logs need to be replayed
Posted by "Brock Noland (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brock Noland updated FLUME-1527:
--------------------------------
Description:
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 (as such nothing is replayed), and restarted we would not have any logs to replay and as such would see the sequence numbers with only current time in ms.
was:
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
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 see the sequence numbers with only current time in ms.
> 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
>
> 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 (as such nothing is replayed), and restarted we would not have any logs to replay and as such would see 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
[jira] [Updated] (FLUME-1527) Seed TransactionID/WriteOrderID in
the case no logs need to be replayed
Posted by "Brock Noland (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brock Noland updated FLUME-1527:
--------------------------------
Description:
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.
was:
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 (as such nothing is replayed), and restarted we would not have any logs to replay and as such would see the sequence numbers with only current time in ms.
> 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
>
> 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