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

[Gracelin Priya <gp...@kodiakptt.com>]

Hello,

Can anyone help me to debug?

I had a four node cluster up and running. Brought down all the nodes and tried starting it again. One of the node is not coming up and not joining the cluster. It is throwing the below error. What is the reason for below error?. Verified that IP configuration is fine.


    Suppressed: class org.apache.ignite.IgniteCheckedException: Failed to connect to address [addr=/0:0:0:0:0:0:0:1%lo:47100, err=Remote node ID is not as expected [expected=fc2bcbe5-2a4b-406b-b60d-69a445f52fd9, rcvd=fad95ab3-d45f-484d-bf24-e5ffad660ec8]]
        at org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:3175)
        ... 16 more
    Caused by: class org.apache.ignite.IgniteCheckedException: Remote node ID is not as expected [expected=fc2bcbe5-2a4b-406b-b60d-69a445f52fd9, rcvd=fad95ab3-d45f-484d-bf24-e5ffad660ec8]
        at org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.safeHandshake(TcpCommunicationSpi.java:3304)
        at org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:3046)
        ... 16 more

Regards,
Priya

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

[aealexsandrov <ae...@gmail.com>]

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 <ar...@cerner.com>]

@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 <e....@gmail.com>]

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.