You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Nikolay Izhikov (Jira)" <ji...@apache.org> on 2020/04/28 13:24:00 UTC
[jira] [Commented] (IGNITE-11687) Concurrent WAL replay & log may
fail with CRC error on read
[ https://issues.apache.org/jira/browse/IGNITE-11687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17094492#comment-17094492 ]
Nikolay Izhikov commented on IGNITE-11687:
------------------------------------------
I'm excluding this ticket from the 2.8.1 due to inactivity.
> Concurrent WAL replay & log may fail with CRC error on read
> -----------------------------------------------------------
>
> Key: IGNITE-11687
> URL: https://issues.apache.org/jira/browse/IGNITE-11687
> Project: Ignite
> Issue Type: Bug
> Components: persistence
> Reporter: Alexey Goncharuk
> Assignee: Dmitriy Govorukhin
> Priority: Critical
> Fix For: 2.9, 2.8.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The cause is the way {{end}} is calculated for WAL iterator:
> {code}
> if (hnd != null)
> end = hnd.position();
> {code}
> {code}
> @Override public FileWALPointer position() {
> lock.lock();
> try {
> return new FileWALPointer(getSegmentId(), (int)written, 0);
> }
> finally {
> lock.unlock();
> }
> }
> {code}
> Consider a partially written entry. In this case, {{written}} has been already updated, concurrent WAL replay will attempt to read the incompletely written record and since {{end}} is not null, iterator will fail with CRC error.
> The issue may be rarely reproduced by {{IgniteWalSerializerVersionTest}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)