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/04/02 15:56:00 UTC

[jira] [Commented] (IGNITE-8114) Add fail recovery mechanism to tracking pages

    [ https://issues.apache.org/jira/browse/IGNITE-8114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16422656#comment-16422656 ] 

ASF GitHub Bot commented on IGNITE-8114:
----------------------------------------

GitHub user EdShangGG opened a pull request:

    https://github.com/apache/ignite/pull/3734

    IGNITE-8114 Add fail recovery mechanism to tracking pages

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-8114

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/3734.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 #3734
    
----
commit e34a82625d7ade969848cbb9fa1073adb66c80d9
Author: Eduard Shangareev <es...@...>
Date:   2018-03-14T13:48:23Z

    IGNITE-8114 Add fail recovery mechanism to tracking pages

----


> Add fail recovery mechanism to tracking pages
> ---------------------------------------------
>
>                 Key: IGNITE-8114
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8114
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Eduard Shangareev
>            Assignee: Eduard Shangareev
>            Priority: Major
>             Fix For: 2.5
>
>
> Now we just assert that last saved tag in tracking page should be not greater than passed one.
> But because of different issues which we don't understand yet, it could happen.
> So, I suggest to handle it by adding new "corruption" state to tracking state. 
> If tracking page is in a corrupted state than we would throw an exception on any querying of the tracking page. Caller will have opportunity to catch the exception and recover page state.



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