Hello! I think you should avoid calling close() on Ignite caches.
If you want to delete cache with all data, call destroy(). If you don't, just leave the IgniteCache object as is. It will be stored in Ignite internals and given back to you for further operations. Regards, -- Ilya Kasnacheev чт, 18 окт. 2018 г. в 11:27, kcheng.mvp <[email protected]>: > here is the document from source code > > I just wondering is the `close` method must be called ? > > for my case, In my kafka consumer, I did some computation and then put the > data into ignite. > > as the message comes in continuous, I just wondering if keep `close` and > `open` frequently will decrease the system performance > > /** > * Closes this cache instance. > * <p> > * For local cache equivalent to {@link #destroy()}. > * For distributed caches, if called on clients, stops client cache, if > called on a server node, > * just closes this cache instance and does not destroy cache data. > * <p> > * After cache instance is closed another {@code IgniteCache} instance > for the same > * cache can be created using {@link Ignite#cache(String)} method. > */ > > > > > > > > > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
