[
https://issues.apache.org/jira/browse/IGNITE-18781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17706339#comment-17706339
]
Sergey Chugunov commented on IGNITE-18781:
------------------------------------------
[~ct7] , from networking point of view presence of seemingly random ports in
logs is totally fine. When you configure ports for discovery and communication
components of Ignite you only specify the ports these components will be
*listening* to for any *incoming* connections.
When a node decides to open an *outgoing* connection it opens it using any port
it can establish a connection through. And there is no configuration to specify
a port or a port range that should be used when opening outgoing connections.
The root cause of the issue may be too restrictive rules set in the firewall or
something else.
> Strange ports used - Failed to process selector key
> ---------------------------------------------------
>
> Key: IGNITE-18781
> URL: https://issues.apache.org/jira/browse/IGNITE-18781
> Project: Ignite
> Issue Type: Bug
> Components: networking
> Affects Versions: 2.14
> Reporter: Christopher Tenter
> Priority: Major
> Attachments: ignitelog.txt
>
>
> A two-node cluster occasionally cannot communicate when ignite uses a strange
> local or remote port. We've opened all ports that are documented here
> [https://ignite.apache.org/docs/latest/clustering/network-configuration]
>
> However, ignite uses a seemingly random port for connecting to the other node
> sometimes. By default all ports are closed in the firewall, so the connection
> fails with message "Failed to process selector key"
>
> Here are some connections that ignite attempts:
> locAddr=/10.125.100.93:20395, rmtAddr=/10.125.100.179:47100
> locAddr=/10.125.100.93:10800, rmtAddr=/10.125.100.93:1851
> locAddr=/10.125.100.93:10800, rmtAddr=/10.125.100.93:1775
> locAddr=/10.125.100.93:1323, rmtAddr=/10.125.100.179:47100
>
> So ports 20395, 1851, 1775, 1323 are used, but they are closed in the
> firewall. The ports change all the time. If I add them to the firewall, it
> doesn't take long until another unknown one pops up. I could not find them
> anywhere in the ignite documentation. Where do they come from and how to fix
> it?
>
> The network settings in the server config looks like this:
> <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">
> <list>
> <value>10.125.100.93</value>
> <value>10.125.100.179</value>
> </list>
> </property>
> </bean>
> </property>
> <property name="localAddress" value="10.125.100.93"/> <!-- other ip on
> other node-->
> </bean>
> </property>
> <property name="transactionConfiguration">
> <bean
> class="org.apache.ignite.configuration.TransactionConfiguration">
> <!--Set the timeout to 20 seconds-->
> <property name="TxTimeoutOnPartitionMapExchange" value="20000"/>
> </bean>
> </property>
> <property name="communicationSpi">
> <bean
> class="org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi">
> <!-- Override timeout. -->
> <property name="SocketWriteTimeout" value="20000"/>
> </bean>
> </property>
>
> Full log output of the "Failed to process selector key" error attached.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
