ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-10348) Safely recreate metastore to mitigate IGNITE-8735
Date Tue, 27 Nov 2018 16:41:00 GMT

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

ASF GitHub Bot commented on IGNITE-10348:

GitHub user SpiderRus opened a pull request:


    IGNITE-10348 Safely recreate metastore to mitigate IGNITE-8735


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

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

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


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #5515
commit efda38b24ddfc7854b7fc15b43a0863de3420091
Author: Alexey Stelmak <spiderru5597@...>
Date:   2018-11-27T16:38:53Z

    Temporary storage


> Safely recreate metastore to mitigate IGNITE-8735
> -------------------------------------------------
>                 Key: IGNITE-10348
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10348
>             Project: Ignite
>          Issue Type: Improvement
>    Affects Versions: 2.4
>            Reporter: Alexey Goncharuk
>            Assignee: Alexey Stelmak
>            Priority: Critical
>             Fix For: 2.8
> We've fixed the issue IGNITE-8735, so new Ignite deployments are not affected by this
issue, but old deployments still may fail if a wrong page was already put to the free list.
We need to find out a way to repair this situation.

This message was sent by Atlassian JIRA

View raw message