Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
MIME-Version: 1.0
Date: Mon, 21 Sep 2015 20:31:57 +0300
Message-ID: 
 <CAPJKmXk3dRCsxkF6p4CCiLUHNVZ0s=CJGxt9DdvC2FOUn_fgcw@mail.gmail.com>
Subject: Client node throws exception when server node killed
From: Artem Shutak <ashutak@gridgain.com>
To: dev@ignite.apache.org
Content-Type: multipart/alternative; boundary=001a1141f3381ad94d05204542ee

--001a1141f3381ad94d05204542ee
Content-Type: text/plain; charset=UTF-8

Igniters,

In process of working on [1] I've found that Ignite client node throws
CacheException which caused by IgniteClientDisconnectedException (stack
trace below) sometimes when I kill one server node at cluster.

It looks like not expected behavior for me. Is it know issue?

My configuration:
- 3 server nodes
- 2 client nodes
- discovery configuration:
        <property name="discoverySpi">
            <bean
class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
                <property name="ipFinder">
                    <bean
class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
                        <property name="addresses">
                            <list>
                                <value>127.0.0.1:47500</value>
                                <value>127.0.0.1:47501</value>
                                <value>127.0.0.1:47502</value>
                            </list>
                        </property>
                    </bean>
                </property>
            </bean>
        </property>

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

-- Artem --

javax.cache.CacheException: class
org.apache.ignite.IgniteClientDisconnectedException: Operation has been
cancelled (client node disconnected).
at
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1621)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.cacheException(IgniteCacheProxy.java:1749)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:815)
at
org.apache.ignite.yardstick.cache.failover.IgniteAtomicRetriesFailoverBenchmark.test(IgniteAtomicRetriesFailoverBenchmark.java:39)
at
org.yardstickframework.impl.BenchmarkRunner$2.run(BenchmarkRunner.java:165)
at java.lang.Thread.run(Thread.java:745)
Caused by: class org.apache.ignite.IgniteClientDisconnectedException:
Operation has been cancelled (client node disconnected).
at
org.apache.ignite.internal.util.IgniteUtils$14.apply(IgniteUtils.java:801)
at
org.apache.ignite.internal.util.IgniteUtils$14.apply(IgniteUtils.java:799)
... 6 more
Caused by: class
org.apache.ignite.internal.IgniteClientDisconnectedCheckedException:
Operation has been cancelled (client node disconnected).
at
org.apache.ignite.internal.processors.cache.GridCacheMvccManager.disconnectedError(GridCacheMvccManager.java:360)
at
org.apache.ignite.internal.processors.cache.GridCacheMvccManager.onDisconnected(GridCacheMvccManager.java:334)
at
org.apache.ignite.internal.processors.cache.GridCacheSharedContext.onDisconnected(GridCacheSharedContext.java:141)
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.onDisconnected(GridCacheProcessor.java:997)
at
org.apache.ignite.internal.IgniteKernal.onDisconnected(IgniteKernal.java:2983)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$5.onDiscovery(GridDiscoveryManager.java:592)
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.notifyDiscovery(ClientImpl.java:2024)
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.notifyDiscovery(ClientImpl.java:2005)
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1422)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)

--001a1141f3381ad94d05204542ee--