Hi,
Yeah, it seems to be that bug.
As far as can see it's resolved and marked to be released as a part of 2.8.
I haven't managed to find that commit in other branches unfortunately.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
gt; <http://org.apache.ignite.spi.discovery.tcp.tcpdiscoveryspi.info/>(117) -
>> Finished serving remote node connection [rmtAddr=/10.0.31.134:42413
>> <http://10.0.31.134:42413/>, rmtPort=42413
>> 2019-10-02 08:44:37 [tcp-disco-s
d serving remote node connection [rmtAddr=/10.0.31.134:42413,
> rmtPort=42413
> 2019-10-02 08:44:37 [tcp-disco-sock-reader-#6] INFO
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.info
> <http://org.apache.ignite.spi.discovery.tcp.tcpdiscoveryspi.info/>(117) -
> Finished serving remote
.discovery.tcp.tcpdiscoveryspi.info/>(117) -
> Finished serving remote node connection [rmtAddr=/10.0.21.167:60763
> <http://10.0.21.167:60763/>, rmtPort=60763
> 2019-10-02 08:44:37 [tcp-disco-ip-finder-cleaner-#5] ERROR
> org.apache.ignite.spi.discov
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.info(117) - Finished
serving remote node connection [rmtAddr=/10.0.21.167:60763, rmtPort=60763
2019-10-02 08:44:37 [tcp-disco-ip-finder-cleaner-#5] ERROR
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.error(137) - Failed to
clean IP finder up.
org.apache.ignite.spi.IgniteSpiException: Failed
