Re: Persistent dataregion config
Hi Andrey, Sorry, Looks like mixed up eviction policy for data region and Expiry Policy. Eviction Policy shouldn't work with persistence, it works only for in memory data regions. Evgenii -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Persistent dataregion config
Andrey, The default value works for most of the cases: https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/util/IgniteUtils.java#L10634 Evgenii чт, 26 мар. 2020 г. в 04:20, Andrey Davydov : > Thanks a lot. What size recommended for checkpoint buffer size? > > > > > On Wed, Mar 25, 2020 at 12:14 AM Evgenii Zhuravlev < > e.zhuravlev...@gmail.com> wrote: > >> Hi Andrey, >> >> After enabling persistence, Ignite itself will be responsible for data >> eviction from memory to disk and eviction mode or threshold can't be >> changed for it. Parameters pageEvictionMode and evictionThreshold related >> to the complete data eviction from Ignite(not from memory to disk) and more >> designed for in memory cases. >> >> 1. Total memory, that will be used in offheap for this persistence region. >> 2. No, for offheap, for this region, will be used ${config.node.memory.max}. >> Also, don't forget about heap and checkpoint buffer size. >> 3. With enabled pageEvictionMode, data will be evicted from disk too. >> >> Evgenii >> >> вт, 24 мар. 2020 г. в 10:23, Andrey Davydov : >> >>> Hello, >>> >>> >>> >>> Please help me to setup data region properly. >>> >>> >>> >>> I would like to have region which can store up to ${config.node.total. >>> memory.max} bytes, but only small part of data in RAM. >>> >>> >>> >>> My current config (Ignite 2.7.6): >>> >>> >>> >>> >> class="org.apache.ignite.configuration.DataRegionConfiguration"> >>> >>> >>> >>> >> value="true"/> >>> >>> >>> >>> >> value="${config.node.memory.initial}"/> >>> >>> >> value="${config.node.memory.max}"/> >>> >>> >>> >>> >> value="RANDOM_2_LRU"/> >>> >>> >> value="${config.node.memory.eviction.threshold}"/> >>> >>> >>> >>> >> value="true"/> >>> >>> >>> >>> >>> >>> Please confirm three points: >>> >>> >>> >>>1. Total size will be ${config.node.memory.max} >>>2. Total used ram size will be approximately >>>${config.node.memory.max}*${config.node.memory.eviction.threshold} >>>3. Data will not be evicted from disk, only from RAM >>> >>> >>> >>> Thanks. >>> >>> Andrey. >>> >>> >>> >>
Re: Persistent dataregion config
Thanks a lot. What size recommended for checkpoint buffer size? On Wed, Mar 25, 2020 at 12:14 AM Evgenii Zhuravlev wrote: > Hi Andrey, > > After enabling persistence, Ignite itself will be responsible for data > eviction from memory to disk and eviction mode or threshold can't be > changed for it. Parameters pageEvictionMode and evictionThreshold related > to the complete data eviction from Ignite(not from memory to disk) and more > designed for in memory cases. > > 1. Total memory, that will be used in offheap for this persistence region. > 2. No, for offheap, for this region, will be used ${config.node.memory.max}. > Also, don't forget about heap and checkpoint buffer size. > 3. With enabled pageEvictionMode, data will be evicted from disk too. > > Evgenii > > вт, 24 мар. 2020 г. в 10:23, Andrey Davydov : > >> Hello, >> >> >> >> Please help me to setup data region properly. >> >> >> >> I would like to have region which can store up to ${config.node.total. >> memory.max} bytes, but only small part of data in RAM. >> >> >> >> My current config (Ignite 2.7.6): >> >> >> >> > class="org.apache.ignite.configuration.DataRegionConfiguration"> >> >> >> >> > value="true"/> >> >> >> >> > value="${config.node.memory.initial}"/> >> >> > value="${config.node.memory.max}"/> >> >> >> >> > value="RANDOM_2_LRU"/> >> >> > value="${config.node.memory.eviction.threshold}"/> >> >> >> >> >> >> >> >> >> >> Please confirm three points: >> >> >> >>1. Total size will be ${config.node.memory.max} >>2. Total used ram size will be approximately ${config.node.memory.max} >>*${config.node.memory.eviction.threshold} >>3. Data will not be evicted from disk, only from RAM >> >> >> >> Thanks. >> >> Andrey. >> >> >> >
Re: Persistent dataregion config
Hi Andrey, After enabling persistence, Ignite itself will be responsible for data eviction from memory to disk and eviction mode or threshold can't be changed for it. Parameters pageEvictionMode and evictionThreshold related to the complete data eviction from Ignite(not from memory to disk) and more designed for in memory cases. 1. Total memory, that will be used in offheap for this persistence region. 2. No, for offheap, for this region, will be used ${config.node.memory.max}. Also, don't forget about heap and checkpoint buffer size. 3. With enabled pageEvictionMode, data will be evicted from disk too. Evgenii вт, 24 мар. 2020 г. в 10:23, Andrey Davydov : > Hello, > > > > Please help me to setup data region properly. > > > > I would like to have region which can store up to ${config.node.total. > memory.max} bytes, but only small part of data in RAM. > > > > My current config (Ignite 2.7.6): > > > > class="org.apache.ignite.configuration.DataRegionConfiguration"> > > > > value="true"/> > > > > value="${config.node.memory.initial}"/> > > value="${config.node.memory.max}"/> > > > > value="RANDOM_2_LRU"/> > > value="${config.node.memory.eviction.threshold}"/> > > > > > > > > > > Please confirm three points: > > > >1. Total size will be ${config.node.memory.max} >2. Total used ram size will be approximately ${config.node.memory.max}* >${config.node.memory.eviction.threshold} >3. Data will not be evicted from disk, only from RAM > > > > Thanks. > > Andrey. > > >
Persistent dataregion config
Hello, Please help me to setup data region properly. I would like to have region which can store up to ${config.node.total.memory.max} bytes, but only small part of data in RAM. My current config (Ignite 2.7.6): Please confirm three points: Total size will be ${config.node.memory.max}Total used ram size will be approximately ${config.node.memory.max}*${config.node.memory.eviction.threshold}Data will not be evicted from disk, only from RAM Thanks.Andrey.