Sergey,
I think your suggestion makes sense. Please make sure that the exception
thrown states that client side caches can only be configured on system
startup.
On Wed, Apr 5, 2017 at 5:43 AM, Sergey Chugunov
wrote:
> In that case I suggest the following solution based on the same model of
> a
In that case I suggest the following solution based on the same model of
allocating memory on node startup.
So, on client nodes if user provides configuration for MemoryPolicies, we
allocate all memory on node startup.
But if no MemoryPolicy configuration is provided on client node startup, no
def
It's abdolutely fine to have local caches on client nodes if an application
needs to cache data locally in hashtable like data structure and talk to it
using Ignite APIs.
The upshot is that this kind of cache can be started on any node and we
should keep supporting this capability in 2.0.
--
Deni
Hello Igniters,
Participating in big effort of reworking cache storage structures
(IGNITE-3477 [1]) I came across a test that looks strange to me:
*CacheStopAndDestroySelfTest::testLocalClose*.
It is very simple: it starts two server nodes and one client node (with
forceServerMode flag set to tru
