All geek questions in one place

Auto increment flag in hazelcast configuration

I am not completely sure of the purpose for the auto-increment flag in the hazelcast XML diagram configuration file. When I disconnected, I see several exceptions in my server instance, complaining that the port is not open (already in use) for port 5701 (since the tiered frame no longer goes to port 5702, etc.). Why does Hazelcast need this property when I use tcp-enabled server setup?

I see the following in my log statements after starting the server, and it looks like it is listening on port 5701 (by default in config):

Members [1] { Member [127.0.0.1]:5701 this } 2014-09-05 05:46:00,407 INFO chcLifecycleService [main] [127.0.0.1]:5701 [dev] [3.2.4] Address[127.0.0.1]:5701 is STARTED 2014-09-05 05:46:00,414 INFO cacnSendServerEmail [main] hazelcast server email notification for server 192.168.110.154 WildMetrix Hazelcast server launched at 192.168.110.154 2014-09-05 05:46:01,336 INFO chpInternalPartitionService [hz._hzInstance_1_dev.cached.thread-1] [127.0.0.1]:5701 [dev] [3.2.4] Initializing cluster partition table first arrangement... 2014-09-05 05:46:01,521 INFO chiDefaultAddressPicker [main] null [dev] [3.2.4] Interfaces is disabled, trying to pick one address from TCP-IP config addresses: [127.0.0.1] 2014-09-05 05:46:01,522 INFO chiDefaultAddressPicker [main] null [dev] [3.2.4] Picked Address[127.0.0.1]:5702, using socket ServerSocket[addr=/0.0.0.0,localport=5702], bind any local is true 2014-09-05 05:46:01,602 INFO chsystem [main] [127.0.0.1]:5702 [dev] [3.2.4] Hazelcast 3.2.4 (20140721) starting at Address[127.0.0.1]:5702 2014-09-05 05:46:01,602 INFO chsystem [main] [127.0.0.1]:5702 [dev] [3.2.4] Copyright (C) 2008-2014 Hazelcast.com 2014-09-05 05:46:01,604 INFO chiNode [main] [127.0.0.1]:5702 [dev] [3.2.4] Creating TcpIpJoiner 2014-09-05 05:46:01,606 INFO chcLifecycleService [main] [127.0.0.1]:5702 [dev] [3.2.4] Address[127.0.0.1]:5702 is STARTING 2014-09-05 05:46:01,619 INFO chcTcpIpJoiner [main] [127.0.0.1]:5702 [dev] [3.2.4] Connecting to possible member: Address[127.0.0.1]:5703 2014-09-05 05:46:01,620 INFO chcTcpIpJoiner [main] [127.0.0.1]:5702 [dev] [3.2.4] Connecting to possible member: Address[127.0.0.1]:5701 2014-09-05 05:46:01,620 INFO chnSocketConnector [hz._hzInstance_2_dev.cached.thread-2] [127.0.0.1]:5702 [dev] [3.2.4] Connecting to /127.0.0.1:5703, timeout: 0, bind-any: true 2014-09-05 05:46:01,621 INFO chnSocketConnector [hz._hzInstance_2_dev.cached.thread-2] [127.0.0.1]:5702 [dev] [3.2.4] Could not connect to: /127.0.0.1:5703. Reason: SocketException[Connection refused to address /127.0.0.1:5703] 2014-09-05 05:46:01,621 INFO chnSocketConnector [hz._hzInstance_2_dev.cached.thread-2] [127.0.0.1]:5702 [dev] [3.2.4] Connecting to /127.0.0.1:5701, timeout: 0, bind-any: true 2014-09-05 05:46:01,628 INFO chnSocketAcceptor [hz._hzInstance_1_dev.IO.thread-Acceptor] [127.0.0.1]:5701 [dev] [3.2.4] Accepting socket connection from /127.0.0.1:46001 2014-09-05 05:46:01,639 INFO chnTcpIpConnectionManager [hz._hzInstance_2_dev.cached.thread-2] [127.0.0.1]:5702 [dev] [3.2.4] 46001 accepted socket connection from /127.0.0.1:5701 2014-09-05 05:46:01,639 INFO chnTcpIpConnectionManager [hz._hzInstance_1_dev.IO.thread-Acceptor] [127.0.0.1]:5701 [dev] [3.2.4] 5701 accepted socket connection from /127.0.0.1:46001 2014-09-05 05:46:38,637 WARN chcTcpIpJoiner [main] [127.0.0.1]:5702 [dev] [3.2.4] Couldn't join to the master : Address[127.0.0.1]:5701 2014-09-05 05:46:38,638 WARN chcTcpIpJoiner [main] [127.0.0.1]:5702 [dev] [3.2.4] Failed to connect, node joined= false, allConnected= false to all other members after 0 seconds. 2014-09-05 05:46:38,638 WARN chcTcpIpJoiner [main] [127.0.0.1]:5702 [dev] [3.2.4] Rebooting after 10 seconds. 2014-09-05 05:46:48,639 INFO chcTcpIpJoiner [main] [127.0.0.1]:5702 [dev] [3.2.4] Connecting to possible member: Address[127.0.0.1]:5703 2014-09-05 05:46:48,639 INFO chnSocketConnector [hz._hzInstance_2_dev.cached.thread-1] [127.0.0.1]:5702 [dev] [3.2.4] Connecting to /127.0.0.1:5703, timeout: 0, bind-any: true 2014-09-05 05:46:48,640 INFO chnSocketConnector [hz._hzInstance_2_dev.cached.thread-1] [127.0.0.1]:5702 [dev] [3.2.4] Could not connect to: /127.0.0.1:5703. Reason: SocketException[Connection refused to address /127.0.0.1:5703] 2014-09-05 05:46:48,640 INFO chcTcpIpJoiner [main] [127.0.0.1]:5702 [dev] [3.2.4] Connecting to possible member: Address[127.0.0.1]:5701 2014-09-05 05:47:14,648 WARN chcTcpIpJoiner [main] [127.0.0.1]:5702 [dev] [3.2.4] Failed to connect, node joined= false, allConnected= false to all other members after 0 seconds. 2014-09-05 05:47:14,648 WARN chcTcpIpJoiner [main] [127.0.0.1]:5702 [dev] [3.2.4] Rebooting after 10 seconds. 2014-09-05 05:47:24,649 INFO chcTcpIpJoiner [main] [127.0.0.1]:5702 [dev] [3.2.4] Connecting to possible member: Address[127.0.0.1]:5703 2014-09-05 05:47:24,649 INFO chcTcpIpJoiner [main] [127.0.0.1]:5702 [dev] [3.2.4] Connecting to possible member: Address[127.0.0.1]:5701 2014-09-05 05:47:24,649 INFO chnSocketConnector [hz._hzInstance_2_dev.cached.thread-2] [127.0.0.1]:5702 [dev] [3.2.4] Connecting to /127.0.0.1:5703, timeout: 0, bind-any: true 2014-09-05 05:47:24,650 INFO chnSocketConnector [hz._hzInstance_2_dev.cached.thread-2] [127.0.0.1]:5702 [dev] [3.2.4] Could not connect to: /127.0.0.1:5703. Reason: SocketException[Connection refused to address /127.0.0.1:5703]
+5
source share
1 answer

The Hazelcast server should try to bind to the port specified in the port property. If the default port is unavailable for binding, Hazelcast must increment the port number (using the number of ports flag) until it receives a free port for binding. If not mistaken, he can try to connect three ports or one by default - he will check and update accordingly. You can set the port auto-increment parameter to false if you want the Hazelcast server to simply bind to one port and not increase it.

 <port auto-increment="true" port-count="100">5701</port>

In addition, make sure that port 5701 is not used by another process and is available for binding, and that there is nothing in the system that would prevent the server from binding on that port, such as any firewall, etc.

+3
source

Source: https://habr.com/ru/post/1201881/

More articles:


All Articles