You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by aMark <fe...@gmail.com> on 2018/02/05 14:31:34 UTC
Upgrading from Ignite-2.1 to Ignite-2.3
Hi
We are using Ignite cache version 2.1. We are using it as persistent store
in Partitioned Mode having 6 data node running. Atomicity mode is
ATOMIC, and Rebalance mode is ASYNC while CacheWriteSynchronizationMode is
FULL_SYNC.
We are upgrading the env to latest Ignite version 2.3. As we are using cache
as persistent store so dont want to start from clean data, we want to keep
existing data persisted with Ignite 2.1.
But when we restart data grid servers after upgrade, we are getting below
exception on some of the nodes :
2018-02-05 14:02:07,403 ERROR [main] {}
org.apache.ignite.internal.IgniteKernal%f011b8f5-8253-4755-84d6-34e5bf47be41
- Got exception while starting (will rollback startup routine). class
org.apache.ignite.IgniteCheckedException: Failed to start manager:
GridManagerAdapter [enabled=true,
name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
at
org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1857)
at
org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1002)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1909)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1652)
at
org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1080)
at
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:998)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:884)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:783)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:653)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:622)
at org.apache.ignite.Ignition.start(Ignition.java:347)
at
com.xxxx.datagrid.AlcyoneDataGridServer.main(AlcyoneDataGridServer.java:63)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to start
SPI: TcpDiscoverySpi [addrRslvr=null, sockTimeout=5000, ackTimeout=5000,
marsh=JdkMarshaller [], reconCnt=10, maxAckTimeout=600000,
forceSrvMode=false, clientReconnectDisabled=false]
at
org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:300)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:882)
at
org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1852)
... 11 more
Caused by: class org.apache.ignite.spi.IgniteSpiException: Local node and
remote node have different version numbers (node will not join, Ignite does
not support rolling updates, so versions must be exactly the same)
[locBuildVer=2.1.0, rmtBuildVer=2.3.0,
locNodeAddrs=[abcd-lapp0003.mgmt.xxxx.org/xx.xx.21.26,
xx.xx.21.26/xx.xx.44.50, abcd-lapp0003.coresit.xxxx.org/xx.xy.216.50,
/127.0.0.1], rmtNodeAddrs=[abcd-lapp0001.mgmt.xxxx.org/xx.xx.21.35,
xx.xx.21.35/xx.xx.44.34, abcd-lapp0001.coresit.xxxx.org/xx.xy.216.29,
/127.0.0.1], locNodeId=7c530b08-3f15-48c3-be1b-4c8a82d28f24,
rmtNodeId=0321de49-8022-434d-b089-5c452d22a405]
at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.checkFailedError(TcpDiscoverySpi.java:1771)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl.joinTopology(ServerImpl.java:919)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl.spiStart(ServerImpl.java:360)
at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.spiStart(TcpDiscoverySpi.java:1846)
at
org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:297)
... 13 more
Is there some guide/URLs which we can take a look and resolve all the known
issue in migration ?
Thanks,
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Upgrading from Ignite-2.1 to Ignite-2.3
Posted by Evgenii Zhuravlev <e....@gmail.com>.
Sorry, it was a mistake in my previous answer, I meant that you should stop
all nodes of version 2.1 at first.
Evgenii
2018-02-05 17:35 GMT+03:00 Evgenii Zhuravlev <e....@gmail.com>:
> Hi,
>
> You witnessed his issue because you have node of the previous version in
> the cluster on the address abcd-lapp0003.mgmt.xxxx.org/xx.xx.21.26. You
> should start all nodes of version 2.1 at first and then start nodes with a
> new version.
>
> Evgenii
>
> 2018-02-05 17:31 GMT+03:00 aMark <fe...@gmail.com>:
>
>> Hi
>>
>>
>> We are using Ignite cache version 2.1. We are using it as persistent store
>> in Partitioned Mode having 6 data node running. Atomicity mode is
>> ATOMIC, and Rebalance mode is ASYNC while CacheWriteSynchronizationMode is
>> FULL_SYNC.
>>
>> We are upgrading the env to latest Ignite version 2.3. As we are using
>> cache
>> as persistent store so dont want to start from clean data, we want to keep
>> existing data persisted with Ignite 2.1.
>>
>> But when we restart data grid servers after upgrade, we are getting below
>> exception on some of the nodes :
>>
>> 2018-02-05 14:02:07,403 ERROR [main] {}
>> org.apache.ignite.internal.IgniteKernal%f011b8f5-8253-4755-
>> 84d6-34e5bf47be41
>> - Got exception while starting (will rollback startup routine). class
>> org.apache.ignite.IgniteCheckedException: Failed to start manager:
>> GridManagerAdapter [enabled=true,
>> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
>> at
>> org.apache.ignite.internal.IgniteKernal.startManager(IgniteK
>> ernal.java:1857)
>> at
>> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1002)
>> at
>> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.
>> start0(IgnitionEx.java:1909)
>> at
>> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.
>> start(IgnitionEx.java:1652)
>> at
>> org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1080)
>> at
>> org.apache.ignite.internal.IgnitionEx.startConfigurations(Ig
>> nitionEx.java:998)
>> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:
>> 884)
>> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:
>> 783)
>> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:
>> 653)
>> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:
>> 622)
>> at org.apache.ignite.Ignition.start(Ignition.java:347)
>> at
>> com.xxxx.datagrid.AlcyoneDataGridServer.main(AlcyoneDataGrid
>> Server.java:63)
>> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to
>> start
>> SPI: TcpDiscoverySpi [addrRslvr=null, sockTimeout=5000, ackTimeout=5000,
>> marsh=JdkMarshaller [], reconCnt=10, maxAckTimeout=600000,
>> forceSrvMode=false, clientReconnectDisabled=false]
>> at
>> org.apache.ignite.internal.managers.GridManagerAdapter.start
>> Spi(GridManagerAdapter.java:300)
>> at
>> org.apache.ignite.internal.managers.discovery.GridDiscoveryM
>> anager.start(GridDiscoveryManager.java:882)
>> at
>> org.apache.ignite.internal.IgniteKernal.startManager(IgniteK
>> ernal.java:1852)
>> ... 11 more
>> Caused by: class org.apache.ignite.spi.IgniteSpiException: Local node and
>> remote node have different version numbers (node will not join, Ignite
>> does
>> not support rolling updates, so versions must be exactly the same)
>> [locBuildVer=2.1.0, rmtBuildVer=2.3.0,
>> locNodeAddrs=[abcd-lapp0003.mgmt.xxxx.org/xx.xx.21.26,
>> xx.xx.21.26/xx.xx.44.50, abcd-lapp0003.coresit.xxxx.org/xx.xy.216.50,
>> /127.0.0.1], rmtNodeAddrs=[abcd-lapp0001.mgmt.xxxx.org/xx.xx.21.35,
>> xx.xx.21.35/xx.xx.44.34, abcd-lapp0001.coresit.xxxx.org/xx.xy.216.29,
>> /127.0.0.1], locNodeId=7c530b08-3f15-48c3-be1b-4c8a82d28f24,
>> rmtNodeId=0321de49-8022-434d-b089-5c452d22a405]
>> at
>> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.checkFai
>> ledError(TcpDiscoverySpi.java:1771)
>> at
>> org.apache.ignite.spi.discovery.tcp.ServerImpl.joinTopology(
>> ServerImpl.java:919)
>> at
>> org.apache.ignite.spi.discovery.tcp.ServerImpl.spiStart(
>> ServerImpl.java:360)
>> at
>> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.spiStart
>> (TcpDiscoverySpi.java:1846)
>> at
>> org.apache.ignite.internal.managers.GridManagerAdapter.start
>> Spi(GridManagerAdapter.java:297)
>> ... 13 more
>> Is there some guide/URLs which we can take a look and resolve all the
>> known
>> issue in migration ?
>>
>> Thanks,
>>
>>
>>
>> --
>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>>
>
>
Re: Upgrading from Ignite-2.1 to Ignite-2.3
Posted by Evgenii Zhuravlev <e....@gmail.com>.
Hi,
You witnessed his issue because you have node of the previous version in
the cluster on the address abcd-lapp0003.mgmt.xxxx.org/xx.xx.21.26. You
should start all nodes of version 2.1 at first and then start nodes with a
new version.
Evgenii
2018-02-05 17:31 GMT+03:00 aMark <fe...@gmail.com>:
> Hi
>
>
> We are using Ignite cache version 2.1. We are using it as persistent store
> in Partitioned Mode having 6 data node running. Atomicity mode is
> ATOMIC, and Rebalance mode is ASYNC while CacheWriteSynchronizationMode is
> FULL_SYNC.
>
> We are upgrading the env to latest Ignite version 2.3. As we are using
> cache
> as persistent store so dont want to start from clean data, we want to keep
> existing data persisted with Ignite 2.1.
>
> But when we restart data grid servers after upgrade, we are getting below
> exception on some of the nodes :
>
> 2018-02-05 14:02:07,403 ERROR [main] {}
> org.apache.ignite.internal.IgniteKernal%f011b8f5-8253-
> 4755-84d6-34e5bf47be41
> - Got exception while starting (will rollback startup routine). class
> org.apache.ignite.IgniteCheckedException: Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at
> org.apache.ignite.internal.IgniteKernal.startManager(
> IgniteKernal.java:1857)
> at
> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1002)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(
> IgnitionEx.java:1909)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(
> IgnitionEx.java:1652)
> at
> org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1080)
> at
> org.apache.ignite.internal.IgnitionEx.startConfigurations(
> IgnitionEx.java:998)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.
> java:884)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.
> java:783)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.
> java:653)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.
> java:622)
> at org.apache.ignite.Ignition.start(Ignition.java:347)
> at
> com.xxxx.datagrid.AlcyoneDataGridServer.main(
> AlcyoneDataGridServer.java:63)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to start
> SPI: TcpDiscoverySpi [addrRslvr=null, sockTimeout=5000, ackTimeout=5000,
> marsh=JdkMarshaller [], reconCnt=10, maxAckTimeout=600000,
> forceSrvMode=false, clientReconnectDisabled=false]
> at
> org.apache.ignite.internal.managers.GridManagerAdapter.
> startSpi(GridManagerAdapter.java:300)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(
> GridDiscoveryManager.java:882)
> at
> org.apache.ignite.internal.IgniteKernal.startManager(
> IgniteKernal.java:1852)
> ... 11 more
> Caused by: class org.apache.ignite.spi.IgniteSpiException: Local node and
> remote node have different version numbers (node will not join, Ignite does
> not support rolling updates, so versions must be exactly the same)
> [locBuildVer=2.1.0, rmtBuildVer=2.3.0,
> locNodeAddrs=[abcd-lapp0003.mgmt.xxxx.org/xx.xx.21.26,
> xx.xx.21.26/xx.xx.44.50, abcd-lapp0003.coresit.xxxx.org/xx.xy.216.50,
> /127.0.0.1], rmtNodeAddrs=[abcd-lapp0001.mgmt.xxxx.org/xx.xx.21.35,
> xx.xx.21.35/xx.xx.44.34, abcd-lapp0001.coresit.xxxx.org/xx.xy.216.29,
> /127.0.0.1], locNodeId=7c530b08-3f15-48c3-be1b-4c8a82d28f24,
> rmtNodeId=0321de49-8022-434d-b089-5c452d22a405]
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.checkFailedError(
> TcpDiscoverySpi.java:1771)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl.
> joinTopology(ServerImpl.java:919)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl.
> spiStart(ServerImpl.java:360)
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.
> spiStart(TcpDiscoverySpi.java:1846)
> at
> org.apache.ignite.internal.managers.GridManagerAdapter.
> startSpi(GridManagerAdapter.java:297)
> ... 13 more
> Is there some guide/URLs which we can take a look and resolve all the known
> issue in migration ?
>
> Thanks,
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>