Ignite Upgrade from 1.9 to 2.3

[Tejashwa Kumar Verma <te...@gmail.com>]

Hi All,

We are upgrading from 1.9 to 2.3 and here we are facing some issue

In 2.3 we are configuring Data Region as below

<property name="dataStorageConfiguration">
         <bean
class="org.apache.ignite.configuration.DataStorageConfiguration">

            <property name="defaultDataRegionConfiguration">
               <bean
class="org.apache.ignite.configuration.DataRegionConfiguration">
                  <property name="name" value="5GB_SWAP_Region_Swapping" />
                 `<property name="initialSize" value="#{100L * 1024 *
1024}" />
                  <property name="maxSize" value="#{5 * 1024L * 1024L *
1024L}" />
                 * <property name="swapPath"
value="/opt/ignite-manager/1.9/api/swap1" />*
*                  <property name="persistenceEnabled" value="false" >*

               </bean>
            </property>
         </bean>


Here we are trying to configure swapPath and *persistenceEnabled is false.*
So i was expecting that once cache with 5GB_SWAP_Region_Swapping region
will be full then data should go to  swapPath. But we are seeing some weird
behavior here and entire data is going in *SWAP. *Can anyone help me here
if i am doing some wrong configuration or my expectations are not correct.



Thanks & Regards
Tejas

Re: Ignite Upgrade from 1.9 to 2.3

[Tejashwa Kumar Verma <te...@gmail.com>]

Thanks Alexey for quick response.


-
Tejas

On Thu, Jan 11, 2018 at 4:51 PM, Alexey Kukushkin <kukushkinalexey@gmail.com
> wrote:

> Ignite native persistence replaces Swapping feature from Ignite 1.x. Use
> native persistence instead of swapping (remove "swapPath" configuration and
> enable persistence).
>
> "swapPath" setting in Ignite 2.x has different semantics: specifying a
> "swapPath" makes Ignite use memory mapped file for the data region instead
> of off-heap RAM. This is why you see all data go to the file.
>

Re: Ignite Upgrade from 1.9 to 2.3

[Alexey Kukushkin <ku...@gmail.com>]

Ignite native persistence replaces Swapping feature from Ignite 1.x. Use
native persistence instead of swapping (remove "swapPath" configuration and
enable persistence).

"swapPath" setting in Ignite 2.x has different semantics: specifying a
"swapPath" makes Ignite use memory mapped file for the data region instead
of off-heap RAM. This is why you see all data go to the file.