You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Dmitriy Pavlov (JIRA)" <ji...@apache.org> on 2018/06/26 16:09:29 UTC

[jira] [Updated] (IGNITE-8661) WALItreater is not stopped if can not deserialize record

     [ https://issues.apache.org/jira/browse/IGNITE-8661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dmitriy Pavlov updated IGNITE-8661:
-----------------------------------
    Fix Version/s:     (was: 2.6)
                   2.7

> WALItreater is not stopped if can not deserialize record 
> ---------------------------------------------------------
>
>                 Key: IGNITE-8661
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8661
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: 2.5
>            Reporter: Dmitriy Govorukhin
>            Assignee: Dmitriy Govorukhin
>            Priority: Major
>             Fix For: 2.7
>
>
> Currently, we have the following code in RecordV1Serializer.readWithCrc:
> {code:java}
> static WALRecord readWithCrc(.....) throws EOFException, IgniteCheckedException {
>   
>     try (FileInput.Crc32CheckingFileInput in = in0.startRead(skipCrc)) {
>       ..... 
>     }
>     catch (EOFException | SegmentEofException | WalSegmentTailReachedException e) {
>         throw e;
>     }
>     catch (Exception e) {
>         throw new IgniteCheckedException("Failed to read WAL record at position: " + startPos, e);
>     }
> }
> {code}
> So, any runtime error will be remapped to IgniteCheckedException, which will lead to iterator stop due to the following code:
> AbstractWalRecordsIterator.advanceRecord:
> {code}
>    try {
>          ......
>         }
>         catch (IOException | IgniteCheckedException e) {
>             if (e instanceof WalSegmentTailReachedException)
>                 throw (WalSegmentTailReachedException)e;
>             if (!(e instanceof SegmentEofException))
>                 handleRecordException(e, actualFilePtr);
>             return null;
>         }
> {code}
> Any IgniteCheckedException will be ignored and iterator goes ahead to the next segment. 
> I suggest to make the following changes:
> 1) It is unexpected behavior, need to fix it. We should only stop iteration on known exceptions
> 2) Also, need to provide ability skip records by type or some pointer for the StandaloneWalRecordsIterator



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)