ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Goncharuk (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-1163) getOrCreateNearCache should work when ignite configuration contains cache configuration
Date Tue, 28 Jul 2015 06:56:04 GMT
Alexey Goncharuk created IGNITE-1163:
----------------------------------------

             Summary: getOrCreateNearCache should work when ignite configuration contains
cache configuration
                 Key: IGNITE-1163
                 URL: https://issues.apache.org/jira/browse/IGNITE-1163
             Project: Ignite
          Issue Type: Task
            Reporter: Alexey Goncharuk
             Fix For: sprint-8


 * Create an Ignite configuration instance that contains cache configuration
 * Start a client node with this configuration
 * On client call {{getOrCreateNearCache}}

Currently in this scenario near cache will not be created because internally an instance of
client cache is created on node start. Later, when {{getOrCreateNearCache}} is called, exchange
happens, but {{GridCacheProcessor#prepareCacheStart}} returns due to the check {{if (sharedCtx.cacheContext(CU.cacheId(cfg.getName()))
!= null)}}

In this case Ignite should check that near cache is being started and current context is not
near, so existing context should be destroyed, all existing cache proxies should be invalidated
and new cache context and cache proxy should be created.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message