Urgent - Using Paired Connections leading to Connection Refuse

classic Classic list List threaded Threaded
2 messages Options
zork zork
Reply | Threaded
Open this post in threaded view
|

Urgent - Using Paired Connections leading to Connection Refuse

Hello,

We are facing a critical issue with Ignite 2.8.

We have two machines in same location running different ignite services.
M1
Ignite server (running on port 48500)
Ignite client-1 (running on port 48100)

M2
Ignite client-2 (running on port 14050)

Port opened between machines:
M2 to M1 - 48500-48520, 48100-48200
M1 to M2 - 14050

Now, M2 is not able to connect to ignite cluster if I set
usePairedConnections to true.
If I have usePairedConnections to false in TCPCommunicationSPI then all
works fine.
 

Here is the related ignite config:
 
  <property name="discoverySpi">
      <bean class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
        <property name="joinTimeout" value="15000" />
        <property name="ClientReconnectDisabled" value="true" />
        <property name="localPort" value="48500" />
        <property name="localPortRange" value="20" />
        <property name="ipFinder">
          <bean
class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
            <property name="addresses">
              <list>
                <value>hkvaspsy-101:48500..48520</value>
              </list>
            </property>
          </bean>
        </property>
      </bean>
    </property>
    <property name="communicationSpi">
      <bean id="communicationSpiBean"
class="org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi">
        <property name="localPort" value="48100" />
        <property name="slowClientQueueLimit" value="100000" />
        <property name="idleConnectionTimeout" value="30000" />
        <property name="usePairedConnections" value="true" />
      </bean>
    </property>
 
 
Connection refused is noticed in the logs on ignite client-2.
 
15:04:06:443908|0327-01043:FFTracer_Ignite [class
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi]: {DEBUG} Action {Failed
to join to address [addr=DELVM-M1/10.101.131.171:48500, recon=false,
errs=[java.net.ConnectException: Connection refused (Connection refused)]]}
Thread {tcp-client-disco-msg-worker-#21%WebCluster%}
15:04:06:443975|0296-01043:FFTracer_Ignite [class
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi]: {DEBUG} Action {Send
join request [addr=DELVM-M1/10.101.131.171:48501, reconnect=false,
locNodeId=de5d623c-2f6b-4c04-a589-e1812ed1e960]} Thread
{tcp-client-disco-msg-worker-#21%WebCluster%}
15:04:06:444578|1556-01043:FFTracer_Ignite [class
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi]: {ERROR} Action
{Exception on joining: Connection refused (Connection refused)} Thread
{tcp-client-disco-msg-worker-#21%WebCluster%}
java.net.ConnectException: Connection refused (Connection refused)
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
    at
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
    at
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
    at java.net.Socket.connect(Socket.java:607)
    at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.openSocket(TcpDiscoverySpi.java:1545)
    at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.openSocket(TcpDiscoverySpi.java:1507)
    at
org.apache.ignite.spi.discovery.tcp.ClientImpl.sendJoinRequest(ClientImpl.java:708)
    at
org.apache.ignite.spi.discovery.tcp.ClientImpl.joinTopology(ClientImpl.java:603)
    at
org.apache.ignite.spi.discovery.tcp.ClientImpl.access$1100(ClientImpl.java:141)
    at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.tryJoin(ClientImpl.java:2027)
    at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1683)
    at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
    at
org.apache.ignite.spi.discovery.tcp.ClientImpl$1.body(ClientImpl.java:302)
    at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:61)
 
Could you please tell why it is failing in case usePairedConnection is set
to true?
Do we also need 48100-48200 ports opened from M1 to M2 as well?
 
Thanks.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
ilya.kasnacheev ilya.kasnacheev
Reply | Threaded
Open this post in threaded view
|

Re: Urgent - Using Paired Connections leading to Connection Refuse

Hello!

Even with unpaired connections you need communication ports available in both directions, unless you enable communication via discovery feature.

Regards,
--
Ilya Kasnacheev


вт, 20 окт. 2020 г. в 21:31, zork <[hidden email]>:
Hello,

We are facing a critical issue with Ignite 2.8.

We have two machines in same location running different ignite services.
M1
Ignite server (running on port 48500)
Ignite client-1 (running on port 48100)

M2
Ignite client-2 (running on port 14050)

Port opened between machines:
M2 to M1 - 48500-48520, 48100-48200
M1 to M2 - 14050

Now, M2 is not able to connect to ignite cluster if I set
usePairedConnections to true.
If I have usePairedConnections to false in TCPCommunicationSPI then all
works fine.


Here is the related ignite config:

  <property name="discoverySpi">
      <bean class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
        <property name="joinTimeout" value="15000" />
        <property name="ClientReconnectDisabled" value="true" />
        <property name="localPort" value="48500" />
        <property name="localPortRange" value="20" />
        <property name="ipFinder">
          <bean
class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
            <property name="addresses">
              <list>
                <value>hkvaspsy-101:48500..48520</value>
              </list>
            </property>
          </bean>
        </property>
      </bean>
    </property>
    <property name="communicationSpi">
      <bean id="communicationSpiBean"
class="org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi">
        <property name="localPort" value="48100" />
        <property name="slowClientQueueLimit" value="100000" />
        <property name="idleConnectionTimeout" value="30000" />
        <property name="usePairedConnections" value="true" />
      </bean>
    </property>


Connection refused is noticed in the logs on ignite client-2.

15:04:06:443908|0327-01043:FFTracer_Ignite [class
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi]: {DEBUG} Action {Failed
to join to address [addr=DELVM-M1/10.101.131.171:48500, recon=false,
errs=[java.net.ConnectException: Connection refused (Connection refused)]]}
Thread {tcp-client-disco-msg-worker-#21%WebCluster%}
15:04:06:443975|0296-01043:FFTracer_Ignite [class
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi]: {DEBUG} Action {Send
join request [addr=DELVM-M1/10.101.131.171:48501, reconnect=false,
locNodeId=de5d623c-2f6b-4c04-a589-e1812ed1e960]} Thread
{tcp-client-disco-msg-worker-#21%WebCluster%}
15:04:06:444578|1556-01043:FFTracer_Ignite [class
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi]: {ERROR} Action
{Exception on joining: Connection refused (Connection refused)} Thread
{tcp-client-disco-msg-worker-#21%WebCluster%}
java.net.ConnectException: Connection refused (Connection refused)
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
    at
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
    at
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
    at java.net.Socket.connect(Socket.java:607)
    at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.openSocket(TcpDiscoverySpi.java:1545)
    at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.openSocket(TcpDiscoverySpi.java:1507)
    at
org.apache.ignite.spi.discovery.tcp.ClientImpl.sendJoinRequest(ClientImpl.java:708)
    at
org.apache.ignite.spi.discovery.tcp.ClientImpl.joinTopology(ClientImpl.java:603)
    at
org.apache.ignite.spi.discovery.tcp.ClientImpl.access$1100(ClientImpl.java:141)
    at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.tryJoin(ClientImpl.java:2027)
    at
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1683)
    at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
    at
org.apache.ignite.spi.discovery.tcp.ClientImpl$1.body(ClientImpl.java:302)
    at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:61)

Could you please tell why it is failing in case usePairedConnection is set
to true?
Do we also need 48100-48200 ports opened from M1 to M2 as well?

Thanks.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/