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/12/10 17:02:00 UTC

[jira] [Commented] (IGNITE-10624) Cache deployment id may be different that cluster-wide after recovery

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

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

GitHub user Jokser opened a pull request:

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

    IGNITE-10624 Update deployment id for recovered cache after join to topology

    

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

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

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

    https://github.com/apache/ignite/pull/5629.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 #5629
    
----
commit 009c617d2fa9c23e58bd0cad18dfdd7d92ebb363
Author: Pavel Kovalenko <jo...@...>
Date:   2018-12-10T17:00:39Z

    IGNITE-10624 Update deployment id for recovered cache after join to topology
    
    Signed-off-by: Pavel Kovalenko <jo...@gmail.com>

----


> Cache deployment id may be different that cluster-wide after recovery
> ---------------------------------------------------------------------
>
>                 Key: IGNITE-10624
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10624
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache, sql
>    Affects Versions: 2.8
>            Reporter: Pavel Kovalenko
>            Assignee: Pavel Kovalenko
>            Priority: Major
>             Fix For: 2.8
>
>
> When schema for a cache is changing (GridQueryProcessor#processSchemaOperationLocal),
> it may produce false-negative "CACHE_NOT_FOUND" message if a cache was started during recovery while cluster-wide descriptor was changed.
> {noformat}
>         if (cacheInfo == null || !F.eq(depId, cacheInfo.dynamicDeploymentId()))
>             throw new SchemaOperationException(SchemaOperationException.CODE_CACHE_NOT_FOUND, cacheName); 
> {noformat}



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