[
https://issues.apache.org/jira/browse/ASTERIXDB-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14956072#comment-14956072
]
ASF subversion and git services commented on ASTERIXDB-1045:
------------------------------------------------------------
Commit a3b2ab489fda346d4c214de71d5c01d4f1ad7d91 in incubator-asterixdb's branch
refs/heads/master from [~imaxon]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-asterixdb.git;h=a3b2ab4 ]
ASTERIXDB-1045: Log analysis fixes
-Avoid using exceptions for control flow in LogRecord
-Rename LogPage and ilk to LogBuffer
-Busywait on read() to fill entire buffer for fillLogBuffer rather than failing
-Distinguish between log truncation and checksum corruption
TODOs:
- Log IO and parsing still happen in lock-step.
- Busywaiting for read to return something other than 0 is unfortunate
Change-Id: I1658e938eb0f199f748407361ffee4833aac661c
Reviewed-on: https://asterix-gerrit.ics.uci.edu/289
Tested-by: Jenkins <[email protected]>
Reviewed-by: Young-Seok Kim <[email protected]>
Reviewed-by: Murtadha Hubail <[email protected]>
> Log analysis after crash may not handle logs with truncated or corrupt
> records correctly
> ----------------------------------------------------------------------------------------
>
> Key: ASTERIXDB-1045
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-1045
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: AsterixDB, Transactions
> Reporter: asterixdb-importer
> Assignee: Ian Maxon
> Priority: Critical
>
> Log analysis after crash may not handle logs with truncated or corrupt
> records correctly
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
