You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Rajarshi Pain <ra...@gmail.com> on 2017/11/29 15:20:53 UTC
Local node and remote node have different version numbers
Hi,
I was working on Ignite 2,3, and my colleague is working on 1.8. We are
running different application on our local machine using the example ignite
xml, but it getting failed with the below exception:-
We are using our local system ip under TcpDiscoverySpi, but still, it is
detecting each other. How I can stop this and not let them discover each
other.
<property name="discoverySpi">
<bean class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
<property name="ipFinder">
<bean class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
<property name="addresses">
<value>10.23.153.56</value>
</property>
Exception:-
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.3.0, rmtBuildVer=1.8.0, locNodeAddrs=[
01HW1083820.India.TCS.com/0:0:0:0:0:0:0:1, /10.23.209.152, /127.0.0.1],
rmtNodeAddrs=[01Hw1083774.India.TCS.com/0:0:0:0:0:0:0:1, /10.23.209.149, /
127.0.0.1], locNodeId=c3e4f1ff-f6d7-4c26-9baf-e04f99a8eaac,
rmtNodeId=75e5e5bc-5de2-484a-9a91-a3a9f2ec48d3]
--
Regards,
Rajarshi Pain
Re: Local node and remote node have different version numbers
Posted by Evgenii Zhuravlev <e....@gmail.com>.
Also, as you saw, example ignite xml has MulticastIpFinder configured, so,
I think it's the root cause. Please make sure that you really started
Ignite with config file, that doesn't have configured MulticastIpFinder,
it's possible that you run node with default example xml config file
Evgenii
2017-11-30 16:30 GMT+03:00 Evgenii Zhuravlev <e....@gmail.com>:
> So, don't use multi cast ip finder at all.
>
> 2017-11-30 15:27 GMT+03:00 Rajarshi Pain <ra...@gmail.com>:
>
>> The code is in client machine so can not share the code, config is there
>> in this mail chain. Yes we are not using multi cast ip. But as we couldn't
>> fix it so my colleague is using the multicast ip that given in ignite
>> website.
>>
>> On Thu 30 Nov, 2017, 15:44 Evgenii Zhuravlev, <e....@gmail.com>
>> wrote:
>>
>>> Are you sure that you are using not Multicast IP finder? Please share
>>> configuration for all nodes that find each other and log files
>>>
>>> 2017-11-30 9:32 GMT+03:00 Rajarshi Pain <ra...@gmail.com>:
>>>
>>>> Hi Evgenii,
>>>>
>>>> We both tried to specify the port, but still we rae getting same error
>>>> if we both running it on the time in our system.
>>>>
>>>> On Wed 29 Nov, 2017, 21:04 Evgenii Zhuravlev, <e....@gmail.com>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> In this case, you should specify ports for addresses, for example:
>>>>>
>>>>> <value>10.23.153.56:47500</value>
>>>>>
>>>>>
>>>>> Evgenii
>>>>>
>>>>>
>>>>> 2017-11-29 18:20 GMT+03:00 Rajarshi Pain <ra...@gmail.com>:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I was working on Ignite 2,3, and my colleague is working on 1.8. We
>>>>>> are running different application on our local machine using the example
>>>>>> ignite xml, but it getting failed with the below exception:-
>>>>>>
>>>>>> We are using our local system ip under TcpDiscoverySpi, but still,
>>>>>> it is detecting each other. How I can stop this and not let them discover
>>>>>> each other.
>>>>>>
>>>>>> <property name="discoverySpi">
>>>>>> <bean class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
>>>>>> <property name="ipFinder">
>>>>>> <bean class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
>>>>>> <property name="addresses">
>>>>>> <value>10.23.153.56</value>
>>>>>>
>>>>>> </property>
>>>>>>
>>>>>>
>>>>>> Exception:-
>>>>>>
>>>>>> 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.3.0, rmtBuildVer=1.8.0,
>>>>>> locNodeAddrs=[01HW1083820.India.TCS.com/0:0:0:0:0:0:0:1, /
>>>>>> 10.23.209.152, /127.0.0.1], rmtNodeAddrs=[01Hw1083774.Indi
>>>>>> a.TCS.com/0:0:0:0:0:0:0:1, /10.23.209.149, /127.0.0.1],
>>>>>> locNodeId=c3e4f1ff-f6d7-4c26-9baf-e04f99a8eaac,
>>>>>> rmtNodeId=75e5e5bc-5de2-484a-9a91-a3a9f2ec48d3]
>>>>>>
>>>>>> --
>>>>>> Regards,
>>>>>> Rajarshi Pain
>>>>>>
>>>>>
>>>>> --
>>>>
>>>> Thanks
>>>> Rajarshi
>>>>
>>>
>>> --
>>
>> Thanks
>> Rajarshi
>>
>
>
Re: Local node and remote node have different version numbers
Posted by Evgenii Zhuravlev <e....@gmail.com>.
So, don't use multi cast ip finder at all.
2017-11-30 15:27 GMT+03:00 Rajarshi Pain <ra...@gmail.com>:
> The code is in client machine so can not share the code, config is there
> in this mail chain. Yes we are not using multi cast ip. But as we couldn't
> fix it so my colleague is using the multicast ip that given in ignite
> website.
>
> On Thu 30 Nov, 2017, 15:44 Evgenii Zhuravlev, <e....@gmail.com>
> wrote:
>
>> Are you sure that you are using not Multicast IP finder? Please share
>> configuration for all nodes that find each other and log files
>>
>> 2017-11-30 9:32 GMT+03:00 Rajarshi Pain <ra...@gmail.com>:
>>
>>> Hi Evgenii,
>>>
>>> We both tried to specify the port, but still we rae getting same error
>>> if we both running it on the time in our system.
>>>
>>> On Wed 29 Nov, 2017, 21:04 Evgenii Zhuravlev, <e....@gmail.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> In this case, you should specify ports for addresses, for example:
>>>>
>>>> <value>10.23.153.56:47500</value>
>>>>
>>>>
>>>> Evgenii
>>>>
>>>>
>>>> 2017-11-29 18:20 GMT+03:00 Rajarshi Pain <ra...@gmail.com>:
>>>>
>>>>> Hi,
>>>>>
>>>>> I was working on Ignite 2,3, and my colleague is working on 1.8. We
>>>>> are running different application on our local machine using the example
>>>>> ignite xml, but it getting failed with the below exception:-
>>>>>
>>>>> We are using our local system ip under TcpDiscoverySpi, but still, it
>>>>> is detecting each other. How I can stop this and not let them discover each
>>>>> other.
>>>>>
>>>>> <property name="discoverySpi">
>>>>> <bean class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
>>>>> <property name="ipFinder">
>>>>> <bean class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
>>>>> <property name="addresses">
>>>>> <value>10.23.153.56</value>
>>>>>
>>>>> </property>
>>>>>
>>>>>
>>>>> Exception:-
>>>>>
>>>>> 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.3.0, rmtBuildVer=1.8.0,
>>>>> locNodeAddrs=[01HW1083820.India.TCS.com/0:0:0:0:0:0:0:1, /
>>>>> 10.23.209.152, /127.0.0.1], rmtNodeAddrs=[01Hw1083774.
>>>>> India.TCS.com/0:0:0:0:0:0:0:1, /10.23.209.149, /127.0.0.1],
>>>>> locNodeId=c3e4f1ff-f6d7-4c26-9baf-e04f99a8eaac,
>>>>> rmtNodeId=75e5e5bc-5de2-484a-9a91-a3a9f2ec48d3]
>>>>>
>>>>> --
>>>>> Regards,
>>>>> Rajarshi Pain
>>>>>
>>>>
>>>> --
>>>
>>> Thanks
>>> Rajarshi
>>>
>>
>> --
>
> Thanks
> Rajarshi
>
Re: Local node and remote node have different version numbers
Posted by Rajarshi Pain <ra...@gmail.com>.
The code is in client machine so can not share the code, config is there in
this mail chain. Yes we are not using multi cast ip. But as we couldn't fix
it so my colleague is using the multicast ip that given in ignite website.
On Thu 30 Nov, 2017, 15:44 Evgenii Zhuravlev, <e....@gmail.com>
wrote:
> Are you sure that you are using not Multicast IP finder? Please share
> configuration for all nodes that find each other and log files
>
> 2017-11-30 9:32 GMT+03:00 Rajarshi Pain <ra...@gmail.com>:
>
>> Hi Evgenii,
>>
>> We both tried to specify the port, but still we rae getting same error if
>> we both running it on the time in our system.
>>
>> On Wed 29 Nov, 2017, 21:04 Evgenii Zhuravlev, <e....@gmail.com>
>> wrote:
>>
>>> Hi,
>>>
>>> In this case, you should specify ports for addresses, for example:
>>>
>>> <value>10.23.153.56:47500</value>
>>>
>>>
>>> Evgenii
>>>
>>>
>>> 2017-11-29 18:20 GMT+03:00 Rajarshi Pain <ra...@gmail.com>:
>>>
>>>> Hi,
>>>>
>>>> I was working on Ignite 2,3, and my colleague is working on 1.8. We are
>>>> running different application on our local machine using the example ignite
>>>> xml, but it getting failed with the below exception:-
>>>>
>>>> We are using our local system ip under TcpDiscoverySpi, but still, it
>>>> is detecting each other. How I can stop this and not let them discover each
>>>> other.
>>>>
>>>> <property name="discoverySpi">
>>>> <bean class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
>>>> <property name="ipFinder">
>>>> <bean class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
>>>> <property name="addresses">
>>>> <value>10.23.153.56</value>
>>>>
>>>> </property>
>>>>
>>>>
>>>> Exception:-
>>>>
>>>> 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.3.0, rmtBuildVer=1.8.0, locNodeAddrs=[
>>>> 01HW1083820.India.TCS.com/0:0:0:0:0:0:0:1, /10.23.209.152, /127.0.0.1],
>>>> rmtNodeAddrs=[01Hw1083774.India.TCS.com/0:0:0:0:0:0:0:1, /10.23.209.149,
>>>> /127.0.0.1], locNodeId=c3e4f1ff-f6d7-4c26-9baf-e04f99a8eaac,
>>>> rmtNodeId=75e5e5bc-5de2-484a-9a91-a3a9f2ec48d3]
>>>>
>>>> --
>>>> Regards,
>>>> Rajarshi Pain
>>>>
>>>
>>> --
>>
>> Thanks
>> Rajarshi
>>
>
> --
Thanks
Rajarshi
Re: Local node and remote node have different version numbers
Posted by Evgenii Zhuravlev <e....@gmail.com>.
Are you sure that you are using not Multicast IP finder? Please share
configuration for all nodes that find each other and log files
2017-11-30 9:32 GMT+03:00 Rajarshi Pain <ra...@gmail.com>:
> Hi Evgenii,
>
> We both tried to specify the port, but still we rae getting same error if
> we both running it on the time in our system.
>
> On Wed 29 Nov, 2017, 21:04 Evgenii Zhuravlev, <e....@gmail.com>
> wrote:
>
>> Hi,
>>
>> In this case, you should specify ports for addresses, for example:
>>
>> <value>10.23.153.56:47500</value>
>>
>>
>> Evgenii
>>
>>
>> 2017-11-29 18:20 GMT+03:00 Rajarshi Pain <ra...@gmail.com>:
>>
>>> Hi,
>>>
>>> I was working on Ignite 2,3, and my colleague is working on 1.8. We are
>>> running different application on our local machine using the example ignite
>>> xml, but it getting failed with the below exception:-
>>>
>>> We are using our local system ip under TcpDiscoverySpi, but still, it
>>> is detecting each other. How I can stop this and not let them discover each
>>> other.
>>>
>>> <property name="discoverySpi">
>>> <bean class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
>>> <property name="ipFinder">
>>> <bean class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
>>> <property name="addresses">
>>> <value>10.23.153.56</value>
>>>
>>> </property>
>>>
>>>
>>> Exception:-
>>>
>>> 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.3.0, rmtBuildVer=1.8.0, locNodeAddrs=[
>>> 01HW1083820.India.TCS.com/0:0:0:0:0:0:0:1, /10.23.209.152, /127.0.0.1],
>>> rmtNodeAddrs=[01Hw1083774.India.TCS.com/0:0:0:0:0:0:0:1, /10.23.209.149,
>>> /127.0.0.1], locNodeId=c3e4f1ff-f6d7-4c26-9baf-e04f99a8eaac,
>>> rmtNodeId=75e5e5bc-5de2-484a-9a91-a3a9f2ec48d3]
>>>
>>> --
>>> Regards,
>>> Rajarshi Pain
>>>
>>
>> --
>
> Thanks
> Rajarshi
>
Re: Local node and remote node have different version numbers
Posted by Rajarshi Pain <ra...@gmail.com>.
Hi Evgenii,
We both tried to specify the port, but still we rae getting same error if
we both running it on the time in our system.
On Wed 29 Nov, 2017, 21:04 Evgenii Zhuravlev, <e....@gmail.com>
wrote:
> Hi,
>
> In this case, you should specify ports for addresses, for example:
>
> <value>10.23.153.56:47500</value>
>
>
> Evgenii
>
>
> 2017-11-29 18:20 GMT+03:00 Rajarshi Pain <ra...@gmail.com>:
>
>> Hi,
>>
>> I was working on Ignite 2,3, and my colleague is working on 1.8. We are
>> running different application on our local machine using the example ignite
>> xml, but it getting failed with the below exception:-
>>
>> We are using our local system ip under TcpDiscoverySpi, but still, it is
>> detecting each other. How I can stop this and not let them discover each
>> other.
>>
>> <property name="discoverySpi">
>> <bean class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
>> <property name="ipFinder">
>> <bean class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
>> <property name="addresses">
>> <value>10.23.153.56</value>
>>
>> </property>
>>
>>
>> Exception:-
>>
>> 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.3.0, rmtBuildVer=1.8.0, locNodeAddrs=[
>> 01HW1083820.India.TCS.com/0:0:0:0:0:0:0:1, /10.23.209.152, /127.0.0.1],
>> rmtNodeAddrs=[01Hw1083774.India.TCS.com/0:0:0:0:0:0:0:1, /10.23.209.149,
>> /127.0.0.1], locNodeId=c3e4f1ff-f6d7-4c26-9baf-e04f99a8eaac,
>> rmtNodeId=75e5e5bc-5de2-484a-9a91-a3a9f2ec48d3]
>>
>> --
>> Regards,
>> Rajarshi Pain
>>
>
> --
Thanks
Rajarshi
Re: Local node and remote node have different version numbers
Posted by Evgenii Zhuravlev <e....@gmail.com>.
Hi,
In this case, you should specify ports for addresses, for example:
<value>10.23.153.56:47500</value>
Evgenii
2017-11-29 18:20 GMT+03:00 Rajarshi Pain <ra...@gmail.com>:
> Hi,
>
> I was working on Ignite 2,3, and my colleague is working on 1.8. We are
> running different application on our local machine using the example ignite
> xml, but it getting failed with the below exception:-
>
> We are using our local system ip under TcpDiscoverySpi, but still, it is
> detecting each other. How I can stop this and not let them discover each
> other.
>
> <property name="discoverySpi">
> <bean class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
> <property name="ipFinder">
> <bean class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
> <property name="addresses">
> <value>10.23.153.56</value>
>
> </property>
>
>
> Exception:-
>
> 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.3.0, rmtBuildVer=1.8.0, locNodeAddrs=[
> 01HW1083820.India.TCS.com/0:0:0:0:0:0:0:1, /10.23.209.152, /127.0.0.1],
> rmtNodeAddrs=[01Hw1083774.India.TCS.com/0:0:0:0:0:0:0:1, /10.23.209.149, /
> 127.0.0.1], locNodeId=c3e4f1ff-f6d7-4c26-9baf-e04f99a8eaac,
> rmtNodeId=75e5e5bc-5de2-484a-9a91-a3a9f2ec48d3]
>
> --
> Regards,
> Rajarshi Pain
>