Whoa! I can see that you have stumbled upon a whole array of usability issues:
- First, when you try to start a cache, it is also started on client node, because it has data region(s) configured. This is where you get the error. I can see that you have node filter specified, apparently it does not help. Please remove dataStorageConfiguration entirely from client node. - Second, when you do setCacheConfigurations(), it has no effect since the node is already started. Then, if you do getOrCreateCache() by name, a default ATOMIC cache is created with no SQL table. Instead, use this: > return ignite.getOrCreateCache(personCacheConfig); I'm still not sure why cache is trying to start on a node despite node filter. I will re-check that. Regards, -- Ilya Kasnacheev чт, 26 дек. 2019 г. в 16:15, ashishb888 <[email protected]>: > Server node: > -2 instances > -Used for data storage > -URL: > > https://github.com/ashishb888/ignite-poc/tree/master/ignite-persistence-data-node > > Client node: > -1 instances > -Used just for creating caches > -URL: > https://github.com/ashishb888/ignite-poc/tree/master/ignite-persistence > > Regards, > Ashish > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
