ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrey Mashenkov <andrey.mashen...@gmail.com>
Subject Re: IgniteCacheProxy connection failure in REPLICATAED mode
Date Thu, 06 Apr 2017 16:56:23 GMT
Hi Rick,

Looks like it is fixed [1] in master and will be available in 2.0 version.
You can try to apply a patch to 1.9 version. PFA patch.

[1] https://issues.apache.org/jira/browse/IGNITE-4473

On Thu, Apr 6, 2017 at 12:05 PM, rick_tem <rvincent@temenos.com> wrote:

> Hi,
>
> I have a cache configuration that looks like this:
>
>                                 <bean class="org.apache.ignite.
> configuration.CacheConfiguration">
>                                         <property name="name"
> value="MCache" />
>                                         <property name="cacheMode"
> value="REPLICATED" />
>                                         <property name="memoryMode"
> value="ONHEAP_TIERED" />
>
>                                         <property name="offHeapMaxMemory"
> value="#{10 * 1024L * 1024L * 1024L}"
> />
>                                         <property name="evictionPolicy">
>
>                                                 <bean
> class="org.apache.ignite.cache.eviction.lru.LruEvictionPolicy">
>
>                                                         <property
> name="maxSize" value="1000000" />
>                                                 </bean>
>                                         </property>
>                                         <property name="atomicityMode"
> value="TRANSACTIONAL" />
>                                         <property name="backups" value="1"
> />
>                                         <property name="writeSynchronizationMode"
> value="FULL_SYNC" />
>                                         <property name="statisticsEnabled"
> value="true" />
>                                 </bean>
>
> I've started two Ignite servers and within JBOSS application server set
> Ignition.setClientMode(true); such that I have 2 servers and 1 client
> (JBOSS) shown in my topology.  When I then terminate one of the Ignite
> servers, I receive the following exception below when my JBOSS app is
> manipulating the cache.  If I am in REPLICATED mode, why doesn't the Ignite
> proxy try the other server automatically on connection failure?  Is there a
> mechanism I should use to protect against connection failure, or how should
> I ensure (in this case a remove operation on the cache) my actions complete
> successfully?
>
> Thanks!
> Rick
>
> Caused by: org.apache.ignite.IgniteClientDisconnectedException: Client
> node
> disconnected: TGrid
>         ... 88 more
> [ERROR] 2017-04-05 14:11:35,675 [tSA 4_1037028145] LOCKING - IgniteCache
> Error
> javax.cache.CacheException: class
> org.apache.ignite.IgniteClientDisconnectedException: Client node
> disconnected: TGrid
>         at
> org.apache.ignite.internal.processors.cache.GridCacheGateway.checkState(
> GridCacheGateway.java:92)
> ~[ignite-core-1.9.0.jar!/:1.9.0]
>         at
> org.apache.ignite.internal.processors.cache.GridCacheGateway.enter(
> GridCacheGateway.java:173)
> ~[ignite-core-1.9.0.jar!/:1.9.0]
>         at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.onEnter(
> IgniteCacheProxy.java:2264)
> ~[ignite-core-1.9.0.jar!/:1.9.0]
>         at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxy.remove(
> IgniteCacheProxy.java:1463)
> ~[ignite-core-1.9.0.jar!/:1.9.0]
>
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/IgniteCacheProxy-connection-
> failure-in-REPLICATAED-mode-tp11769.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>



-- 
Best regards,
Andrey V. Mashenkov

Mime
View raw message