You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/07/25 12:54:00 UTC
[jira] [Commented] (IGNITE-9050) WALIterator should throw an
exception if iterator stopped in the WAL archive but not in WAL work
[ https://issues.apache.org/jira/browse/IGNITE-9050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16555602#comment-16555602 ]
ASF GitHub Bot commented on IGNITE-9050:
----------------------------------------
GitHub user DmitriyGovorukhin opened a pull request:
https://github.com/apache/ignite/pull/4429
IGNITE-9050 WALIterator should throw an exception if iterator stopped in the WAL archive but not in WAL work
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9050
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4429.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4429
----
commit 6fa61d3246f59fe18b4a7c1168ecb33cea59dac9
Author: Dmitriy Govorukhin <dm...@...>
Date: 2018-07-25T12:41:26Z
IGNITE-9050 WALIterator should throw an exception if iterator stopped in the WAL archive but not in WAL work.
----
> WALIterator should throw an exception if iterator stopped in the WAL archive but not in WAL work
> ------------------------------------------------------------------------------------------------
>
> Key: IGNITE-9050
> URL: https://issues.apache.org/jira/browse/IGNITE-9050
> Project: Ignite
> Issue Type: Bug
> Reporter: Dmitriy Govorukhin
> Assignee: Dmitriy Govorukhin
> Priority: Major
> Fix For: 2.7
>
>
> The iterator will stop iteration if next WAL record pointer is not equals expected (WalSegmentTailReachedException), if it happens during iteration over segments in WAL archive, this means WAL is corrupted and we cannot ignore this, WAL log is not fully read.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)