Cristian, I don't see any critical consequences, if you set IGNITE_EXCHANGE_HISTORY_SIZE to 0 on clients. Exchange futures just will be removed after each exchange. By default they are removed only once in a while. Don't do it on server nodes though. Coordinator needs exchange history.
Your problem sounds similar to the following issues: IGNITE-7918 <https://issues.apache.org/jira/browse/IGNITE-7918>, IGNITE-7319 <https://issues.apache.org/jira/browse/IGNITE-7319>. Try updating to one of the nightly builds: https://ignite.apache.org/download.cgi#nightly-builds Or you can wait for Ignite 2.7. Its release date is right around the corner. Denis ср, 31 окт. 2018 г. в 21:49, Cristian Bordei <borde...@yahoo.com>: > Hello, > > We are using Ignite 2.6.0 and we notice on our java app configured as > Ignite client that the memory is increasing too much (approx 5GB). We > succeeded to fix this by setting the value of > IGNITE_EXCHANGE_HISTORY_SIZE to a lower size than 1000. > > My question is which will be the impact if we set the value > of IGNITE_EXCHANGE_HISTORY_SIZE to 0 on the java clients side. > > Our configuration is as follow: > - two Ignite servers in cluster mode. 128 GB ram and 8 core cpu > - 20 java apps configured as Ignite clients. > IgniteConfiguration igniteConfiguration = new IgniteConfiguration(); > igniteConfiguration.setClientMode(true); > > Our use case suppose to destroy all 400 caches every day and recreate > another ones back again. The reuse of the cache is not possible. > > Thank you, > Cristi > > Sent from Yahoo Mail on Android > <https://go.onelink.me/107872968?pid=InProduct&c=Global_Internal_YGrowth_AndroidEmailSig__AndroidUsers&af_wl=ym&af_sub1=Internal&af_sub2=Global_YGrowth&af_sub3=EmailSignature> >