[
https://issues.apache.org/jira/browse/IGNITE-10624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721317#comment-16721317
]
Ignite TC Bot commented on IGNITE-10624:
----------------------------------------
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Hibernate 1{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2545873]]
* HibernateL2CacheTransactionalSelfTest.testRegionClear (last started)
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2540236&buildTypeId=IgniteTests24Java8_RunAll]
> 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)
