单个Ignite节点不会停止TCP发现 [英] Single Ignite node does not stop TCP discovery

查看:109
本文介绍了单个Ignite节点不会停止TCP发现的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

与我的应用程序一起运行的单个ignite节点,由于ignite不断尝试寻找其他节点而无法启动

Single ignite node running with my application and it doesn't start because ignite constantly tries to find some other node

日志中充满以下消息:

o.a.i.s.d.tcp.TcpDiscoverySpi - TCP discovery accepted incoming connection [rmtAddr=/127.0.0.1, rmtPort=59459]
o.a.i.s.d.tcp.TcpDiscoverySpi - TCP discovery spawning a new thread for connection [rmtAddr=/127.0.0.1, rmtPort=59459]
o.a.i.s.d.tcp.TcpDiscoverySpi - Started serving remote node connection [rmtAddr=/127.0.0.1:59459, rmtPort=59459]
o.a.i.s.d.tcp.TcpDiscoverySpi - Finished serving remote node connection [rmtAddr=/127.0.0.1:59459, rmtPort=59459

为DiscoverySpi点燃配置:

Ignite config for discoverySpi:

<property name="discoverySpi">
    <bean class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
        <property name="localPort" value="48550"/>
        <property name="localPortRange" value="1"/>
        <property name="ipFinder">
            <bean class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
                <property name="addresses">
                    <list>
                        <value>myNode:48550</value>
                    </list>
                </property>
            </bean>
        </property>
    </bean>
</property>

配置中是否缺少任何可以解决问题的东西?如果未指定端口范围,为什么Ignite甚至尝试在其他端口上找到节点?

Is there anything in config that I'm missing that would've solved the problem? Why does Ignite even attempt to find node on other port if port range is not specified?

推荐答案

网络接口一定很混乱.尝试指定 127.0.0.1:48550 而不是 myNode:48550 .或者,您可以设置 TcpDiscoverySpi#localAddress myNode .

There must be a confusion of network interfaces. Try specifying 127.0.0.1:48550 instead of myNode:48550. Or you can set TcpDiscoverySpi#localAddress to myNode.

这篇关于单个Ignite节点不会停止TCP发现的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆