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

2018-04-04 Thread aealexsandrov
Hi, You can configure TcpCommunicationSpi: TcpCommunicationSpi communicationSpi = new TcpCommunicationSpi(); communicationSpi.setLocalAddress(localAddress); communicationSpi.setLocalPort(cc.getCommunicationLocalPort()); communicationSpi.setLocalPortRange(cc.getPort

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

2018-04-04 Thread 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

2017-08-03 Thread 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