Client can have only LOCAL cache and NearCache that is frontend to partitioned, see [1]. Moreover, client node requires live server node in topology.
However, you can try to force "server" mode on client node (via *TcpDiscoverySpi.setForceServerMode(true)*) to start it without any servers and use LOCAL cache with read-through. [1] https://apacheignite.readme.io/docs/clients-vs-servers#creating-distributed-caches On Tue, Apr 4, 2017 at 10:56 AM, ALEKSEY KUZNETSOV <[email protected] > wrote: > client node doesnt store cache entries, at all ? > > вт, 4 апр. 2017 г. в 9:42, Andrey Mashenkov <[email protected]>: > >> Hi Sweta, >> >> You should to start server node to Ignite could keep cache data in >> memory. >> >> On Tue, Apr 4, 2017 at 8:43 AM, sweta Das <[email protected]> wrote: >> >> Hi >> I have few clarifications on the read and write through implementation of >> ignite cache. >> I have a mysql database with a simple table (1 int key and 2 columns of >> String). >> I know that I have to start a ignite client node with cache store >> configuration. But do I also need to start the server node passing the jdbc >> driver connection details in the spring xml file? >> >> >> >> >> >> -- >> Best regards, >> Andrey V. Mashenkov >> > -- > > *Best Regards,* > > *Kuznetsov Aleksey* > -- Best regards, Andrey V. Mashenkov
