You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by Valentin Kulichenko <va...@gmail.com> on 2015/11/06 00:27:56 UTC
127.0.0.1 in VmIpFinder
Igniters,
I just tried to switch from multicast to VM IP finder in example-ignite.xml
and nodes stopped joining each other. If I start two servers, they both
start with order=1; if I start a server and then a client, the client never
joins.
Can someone else try to do this and see if it's reproduced? For me this
behavior seems very confusing. And actually it means that our examples
don't work out of the box with disabled multicast.
This user seems to have the same issue:
http://apache-ignite-users.70518.x6.nabble.com/Unable-to-connect-to-Local-Node-Only-td1852.html
-Val
Re: 127.0.0.1 in VmIpFinder
Posted by Denis Magda <dm...@gridgain.com>.
The issue wasn't reproduced on my Mac running under El Captain.
On 11/10/2015 3:30 PM, Denis Magda wrote:
> Val,
>
> I've tried to run the nodes using the configuration discussed below on
> OS X Yosemity.
> Works perfectly fine, both nodes joined the topology and see each other.
>
> Will try to check on OS X El Captain a bit later.
>
> BTW, the problem may be in IPv6. I googled for post [1]. The issue
> discussed there is not completely the same but quite similar.
> Could you disable IPv6 on your side and see whether it works or not?
>
> [1]
> http://superuser.com/questions/830920/curl-local-host-names-on-mac-os-x-yosemite
>
> --
> Denis
>
> On 11/6/2015 4:35 AM, Andrey Gura wrote:
>> I tried it on Linux and Windows 7.
>>
>> On Fri, Nov 6, 2015 at 3:51 AM, Valentin Kulichenko <
>> valentin.kulichenko@gmail.com> wrote:
>>
>>> Thanks, Andrey. What OS are you on? Can someone try this on Mac?
>>>
>>> For me second node can't join because it can't connect to
>>> 127.0.0.1:47500
>>> for some reason. I can't do this with telnet either, which is confusing
>>> because the first one binds to 0.0.0.0 and therefore should be
>>> accessible
>>> via all interfaces.
>>>
>>> -Val
>>>
>>> On Thu, Nov 5, 2015 at 4:45 PM, Andrey Gura <ag...@gridgain.com> wrote:
>>>
>>>> Val,
>>>>
>>>> I do it every day and do not have any problems. I tried it now on
>>>> newest
>>>> master branch and again - no problems.
>>>>
>>>> I just comment one line and uncomment other in config:
>>>>
>>>> <bean
>>>>
>>>>
>>> class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
>>>
>>>> <!--<bean
>>>>
>>>>
>>> class="org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder">-->
>>>
>>>> <property name="addresses">
>>>> <list>
>>>> <!-- In distributed environment,
>>>> replace
>>>> with actual host IP address. -->
>>>> <value>127.0.0.1:47500..47509</value>
>>>> </list>
>>>> </property>
>>>> </bean>
>>>>
>>>>
>>>>
>>>> On Fri, Nov 6, 2015 at 2:27 AM, Valentin Kulichenko <
>>>> valentin.kulichenko@gmail.com> wrote:
>>>>
>>>>> Igniters,
>>>>>
>>>>> I just tried to switch from multicast to VM IP finder in
>>>> example-ignite.xml
>>>>> and nodes stopped joining each other. If I start two servers, they
>>>>> both
>>>>> start with order=1; if I start a server and then a client, the client
>>>> never
>>>>> joins.
>>>>>
>>>>> Can someone else try to do this and see if it's reproduced? For me
>>>>> this
>>>>> behavior seems very confusing. And actually it means that our
>>>>> examples
>>>>> don't work out of the box with disabled multicast.
>>>>>
>>>>> This user seems to have the same issue:
>>>>>
>>>>>
>>> http://apache-ignite-users.70518.x6.nabble.com/Unable-to-connect-to-Local-Node-Only-td1852.html
>>>
>>>>> -Val
>>>>>
>>>>
>>>>
>>>> --
>>>> Andrey Gura
>>>> GridGain Systems, Inc.
>>>> www.gridgain.com
>>>>
>>
>>
>
Re: 127.0.0.1 in VmIpFinder
Posted by Denis Magda <dm...@gridgain.com>.
Val,
I've tried to run the nodes using the configuration discussed below on
OS X Yosemity.
Works perfectly fine, both nodes joined the topology and see each other.
Will try to check on OS X El Captain a bit later.
BTW, the problem may be in IPv6. I googled for post [1]. The issue
discussed there is not completely the same but quite similar.
Could you disable IPv6 on your side and see whether it works or not?
[1]
http://superuser.com/questions/830920/curl-local-host-names-on-mac-os-x-yosemite
--
Denis
On 11/6/2015 4:35 AM, Andrey Gura wrote:
> I tried it on Linux and Windows 7.
>
> On Fri, Nov 6, 2015 at 3:51 AM, Valentin Kulichenko <
> valentin.kulichenko@gmail.com> wrote:
>
>> Thanks, Andrey. What OS are you on? Can someone try this on Mac?
>>
>> For me second node can't join because it can't connect to 127.0.0.1:47500
>> for some reason. I can't do this with telnet either, which is confusing
>> because the first one binds to 0.0.0.0 and therefore should be accessible
>> via all interfaces.
>>
>> -Val
>>
>> On Thu, Nov 5, 2015 at 4:45 PM, Andrey Gura <ag...@gridgain.com> wrote:
>>
>>> Val,
>>>
>>> I do it every day and do not have any problems. I tried it now on newest
>>> master branch and again - no problems.
>>>
>>> I just comment one line and uncomment other in config:
>>>
>>> <bean
>>>
>>>
>> class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
>>> <!--<bean
>>>
>>>
>> class="org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder">-->
>>> <property name="addresses">
>>> <list>
>>> <!-- In distributed environment, replace
>>> with actual host IP address. -->
>>> <value>127.0.0.1:47500..47509</value>
>>> </list>
>>> </property>
>>> </bean>
>>>
>>>
>>>
>>> On Fri, Nov 6, 2015 at 2:27 AM, Valentin Kulichenko <
>>> valentin.kulichenko@gmail.com> wrote:
>>>
>>>> Igniters,
>>>>
>>>> I just tried to switch from multicast to VM IP finder in
>>> example-ignite.xml
>>>> and nodes stopped joining each other. If I start two servers, they both
>>>> start with order=1; if I start a server and then a client, the client
>>> never
>>>> joins.
>>>>
>>>> Can someone else try to do this and see if it's reproduced? For me this
>>>> behavior seems very confusing. And actually it means that our examples
>>>> don't work out of the box with disabled multicast.
>>>>
>>>> This user seems to have the same issue:
>>>>
>>>>
>> http://apache-ignite-users.70518.x6.nabble.com/Unable-to-connect-to-Local-Node-Only-td1852.html
>>>> -Val
>>>>
>>>
>>>
>>> --
>>> Andrey Gura
>>> GridGain Systems, Inc.
>>> www.gridgain.com
>>>
>
>
Re: 127.0.0.1 in VmIpFinder
Posted by Andrey Gura <ag...@gridgain.com>.
I tried it on Linux and Windows 7.
On Fri, Nov 6, 2015 at 3:51 AM, Valentin Kulichenko <
valentin.kulichenko@gmail.com> wrote:
> Thanks, Andrey. What OS are you on? Can someone try this on Mac?
>
> For me second node can't join because it can't connect to 127.0.0.1:47500
> for some reason. I can't do this with telnet either, which is confusing
> because the first one binds to 0.0.0.0 and therefore should be accessible
> via all interfaces.
>
> -Val
>
> On Thu, Nov 5, 2015 at 4:45 PM, Andrey Gura <ag...@gridgain.com> wrote:
>
> > Val,
> >
> > I do it every day and do not have any problems. I tried it now on newest
> > master branch and again - no problems.
> >
> > I just comment one line and uncomment other in config:
> >
> > <bean
> >
> >
> class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
> > <!--<bean
> >
> >
> class="org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder">-->
> > <property name="addresses">
> > <list>
> > <!-- In distributed environment, replace
> > with actual host IP address. -->
> > <value>127.0.0.1:47500..47509</value>
> > </list>
> > </property>
> > </bean>
> >
> >
> >
> > On Fri, Nov 6, 2015 at 2:27 AM, Valentin Kulichenko <
> > valentin.kulichenko@gmail.com> wrote:
> >
> > > Igniters,
> > >
> > > I just tried to switch from multicast to VM IP finder in
> > example-ignite.xml
> > > and nodes stopped joining each other. If I start two servers, they both
> > > start with order=1; if I start a server and then a client, the client
> > never
> > > joins.
> > >
> > > Can someone else try to do this and see if it's reproduced? For me this
> > > behavior seems very confusing. And actually it means that our examples
> > > don't work out of the box with disabled multicast.
> > >
> > > This user seems to have the same issue:
> > >
> > >
> >
> http://apache-ignite-users.70518.x6.nabble.com/Unable-to-connect-to-Local-Node-Only-td1852.html
> > >
> > > -Val
> > >
> >
> >
> >
> > --
> > Andrey Gura
> > GridGain Systems, Inc.
> > www.gridgain.com
> >
>
--
Andrey Gura
GridGain Systems, Inc.
www.gridgain.com
Re: 127.0.0.1 in VmIpFinder
Posted by Valentin Kulichenko <va...@gmail.com>.
Thanks, Andrey. What OS are you on? Can someone try this on Mac?
For me second node can't join because it can't connect to 127.0.0.1:47500
for some reason. I can't do this with telnet either, which is confusing
because the first one binds to 0.0.0.0 and therefore should be accessible
via all interfaces.
-Val
On Thu, Nov 5, 2015 at 4:45 PM, Andrey Gura <ag...@gridgain.com> wrote:
> Val,
>
> I do it every day and do not have any problems. I tried it now on newest
> master branch and again - no problems.
>
> I just comment one line and uncomment other in config:
>
> <bean
>
> class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
> <!--<bean
>
> class="org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder">-->
> <property name="addresses">
> <list>
> <!-- In distributed environment, replace
> with actual host IP address. -->
> <value>127.0.0.1:47500..47509</value>
> </list>
> </property>
> </bean>
>
>
>
> On Fri, Nov 6, 2015 at 2:27 AM, Valentin Kulichenko <
> valentin.kulichenko@gmail.com> wrote:
>
> > Igniters,
> >
> > I just tried to switch from multicast to VM IP finder in
> example-ignite.xml
> > and nodes stopped joining each other. If I start two servers, they both
> > start with order=1; if I start a server and then a client, the client
> never
> > joins.
> >
> > Can someone else try to do this and see if it's reproduced? For me this
> > behavior seems very confusing. And actually it means that our examples
> > don't work out of the box with disabled multicast.
> >
> > This user seems to have the same issue:
> >
> >
> http://apache-ignite-users.70518.x6.nabble.com/Unable-to-connect-to-Local-Node-Only-td1852.html
> >
> > -Val
> >
>
>
>
> --
> Andrey Gura
> GridGain Systems, Inc.
> www.gridgain.com
>
Re: 127.0.0.1 in VmIpFinder
Posted by Andrey Gura <ag...@gridgain.com>.
Val,
I do it every day and do not have any problems. I tried it now on newest
master branch and again - no problems.
I just comment one line and uncomment other in config:
<bean
class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
<!--<bean
class="org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder">-->
<property name="addresses">
<list>
<!-- In distributed environment, replace
with actual host IP address. -->
<value>127.0.0.1:47500..47509</value>
</list>
</property>
</bean>
On Fri, Nov 6, 2015 at 2:27 AM, Valentin Kulichenko <
valentin.kulichenko@gmail.com> wrote:
> Igniters,
>
> I just tried to switch from multicast to VM IP finder in example-ignite.xml
> and nodes stopped joining each other. If I start two servers, they both
> start with order=1; if I start a server and then a client, the client never
> joins.
>
> Can someone else try to do this and see if it's reproduced? For me this
> behavior seems very confusing. And actually it means that our examples
> don't work out of the box with disabled multicast.
>
> This user seems to have the same issue:
>
> http://apache-ignite-users.70518.x6.nabble.com/Unable-to-connect-to-Local-Node-Only-td1852.html
>
> -Val
>
--
Andrey Gura
GridGain Systems, Inc.
www.gridgain.com