[
https://issues.apache.org/jira/browse/IGNITE-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125683#comment-15125683
]
Alexey Kuznetsov commented on IGNITE-2037:
------------------------------------------
Ken,
I opened this issue because I know that client nodes should not start caches,
but for some reason LOCAL cache is started and worked fine on client node.
For me it is OK, we could treat LOCAL cache as HashMap on "steroids" - all
powerful Ignite features available for LOCAL caches (transactions, evictions,
...).
And for some user cases it could be useful. I think we should some how update
javadocs and documentation about such feature (side effect???) of Ignite.
> Update javadocs and documentation about LOCAL cache could be created on
> client node
> -----------------------------------------------------------------------------------
>
> Key: IGNITE-2037
> URL: https://issues.apache.org/jira/browse/IGNITE-2037
> Project: Ignite
> Issue Type: Bug
> Components: cache, newbie
> Affects Versions: ignite-1.4
> Reporter: Alexey Kuznetsov
> Assignee: Alexey Kuznetsov
> Priority: Trivial
> Fix For: 1.6
>
>
> Code that show local cache on client node:
> {code}
> public class LocalCacheOnClient {
> public static void main(String[] args) throws IgniteException {
> IgniteConfiguration cfgSrv = new IgniteConfiguration();
> cfgSrv.setGridName("srv");
> Ignite n1 = Ignition.start(cfgSrv);
> IgniteConfiguration cfgClm = new IgniteConfiguration();
> cfgClm.setGridName("cln");
> cfgClm.setClientMode(true);
> Ignite n2 = Ignition.start(cfgClm);
> CacheConfiguration<Integer, Integer> ccfg = new
> CacheConfiguration<>("local");
> ccfg.setCacheMode(CacheMode.LOCAL);
> IgniteCache<Integer, Integer> c = n2.getOrCreateCache(ccfg);
> c.put(1, 100);
> n1.close(); // stop server node
> c.put(2, 200); // local cache works fine.
> System.out.println(c.get(1));
> System.out.println(c.get(2));
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
