Hi Usman! "Timeout has occurred", printed by *GridTimeoutProcessor*, is an internal debug message, which tells you, that some scheduled task is getting executed. It's not an error.
And you shouldn't be worried about "connection refused" exceptions on the node startup. They are thrown for all rejected addresses, that are specified in IP finder. This is also a part of debug information. So is there something that doesn't work on topology with 2 nodes? Except for those messages, that you see in log? Denis вт, 2 янв. 2018 г. в 8:37, Usman Waheed <[email protected]>: > For the connection refused error in the logs we have set ipFinder property > to: > > <property name="discoverySpi"> > <bean > class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi"> > <property name="socketTimeout" value="600000"/> > <property name="networkTimeout" value="600000"/> > <property name="joinTimeout" value="600000" /> > <property name="ackTimeout" value="50000" /> > <property name="statisticsPrintFrequency" value="20000" /> > > <property name="ipFinder"> > <bean > > class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder"> > <property name="addresses"> > <list> > <value>10.145.1.14:47500..47509</value> > <value>10.145.1.15:47500..47509</value> > </list> > </property> > </bean> > </property> > </bean> > </property> > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
