Hello! I don't think you can start a new data region dynamically. This means that you need to think out all the data regions in advance.
Note that it highly adviced to never hit the limit of data region by getting IgniteOutOfMemory. You would need to use some other means to limit sizes of your caches. This will also mean that you don't need that many data regions. Regards, -- Ilya Kasnacheev ср, 14 нояб. 2018 г. в 23:02, [email protected] < [email protected]>: > Hi, > > We are using Ignite 1.9 OffHeapCache with swap space disabled, we have > about > 80 different caches, all are defined programmatically. Some have the > expiry, > some have eviction policy. > > We are trying to upgrade to 2.6 and need help - > > 1. Many API from 1.9 is no longer supported or deprecated in 2.6? > Example - cache configuration no longer seems to have the ability to define > EvictionPolicy, startSize, offHeapMaxMemory, swap space disable. Most of > these settings are available on Data Region instead, does that mean each > cache needs to be defined as a separate data region to have that kind of > control? We tried to do same by defining data region programmatically and > use that region while programmatic cache definition, however, it fails with > data region not found. > > 2. What strategy or best practice to be used for defining data region? > Should we use data region to group then based on usecase or volatility or > other aspects? In that case how to control size for each type of cache? > > Thanks, > -Sam > > > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
