ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From torjt <jeremy.tor...@gmail.com>
Subject Client Near Cache Configuration Lost after Cluster Node Removed
Date Mon, 16 Oct 2017 21:54:08 GMT
Hello All,

We are having an issue with Ignite client near caches being "lost" upon a
cluster node being removed from the Ignite cluster.  Furthermore, using
version 2.1.0, we are seeing this issue when another client joins the
topology.  I built Ignite from GIT today, 10/16/17, with the latest changes,
ver. 2.3.0-SNAPSHOT.  As of version 2.3.0-SNAPSHOT, bringing clients up/down
does not cause an active client to lose its near cache and performance is
good.  However, when we remove a node from the cluster, the client
immediately communicates with the cluster and disregards its near cache. 
Restarting the client remedies the issue.

The following is the steps to reproduce the issue:
Apache Ignite Version:
1.  Start 2 Ignite servers
2.  Start client with caches configured as near-cache
3.  Access caches
4.  Stop node client is connected to
4a.  Client immediately bypasses near cache and access "cluster" for cache

Sent from: http://apache-ignite-users.70518.x6.nabble.com/

View raw message