You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Kovalenko (JIRA)" <ji...@apache.org> on 2018/12/13 10:06:04 UTC

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

     [ https://issues.apache.org/jira/browse/IGNITE-10624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavel Kovalenko updated IGNITE-10624:
-------------------------------------
    Summary: Cache deployment id may be different than cluster-wide after recovery  (was: Cache deployment id may be different that cluster-wide after recovery)

> Cache deployment id may be different than 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)