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());

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
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

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

2017-08-01 Thread Gracelin Priya
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