Re: Remote node ID is not as expected - New Node not coming up

[aealexsandrov]

Hi,

You can configure TcpCommunicationSpi:

TcpCommunicationSpi communicationSpi = new TcpCommunicationSpi();
communicationSpi.setLocalAddress(localAddress);
communicationSpi.setLocalPort(cc.getCommunicationLocalPort());
communicationSpi.setLocalPortRange(cc.getPortRange());

Please take a look at documentation:

https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/spi/communication/tcp/TcpCommunicationSpi.html#setLocalPort-int-

Best Regards,
Andrei



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

Re: Remote node ID is not as expected - New Node not coming up

[ak47]

@ezhuravlev
how can we set different localport?



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

Re: Remote node ID is not as expected - New Node not coming up

[ezhuravlev]

Hello,

Looks like you have you have nodes on different hosts with same ports. Do
you have other exceptions in log? Even if he failed to connect to this node
through localhost address, it should try to connect to other addresses of
node fc2bcbe5-2a4b-406b-b60d-69a445f52fd9. Also, on which addreses this node
were binded?

To avoid it you can set different locaPort on different nodes, even if they
hosts on different machines or set manually localHost for each node.

Evgenii



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Remote-node-ID-is-not-as-expected-New-Node-not-coming-up-tp15858p15940.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.