scopo del contrassegno di incremento automatico nella configurazione di nocciolato

Question

Non sono completamente sicuro dello scopo del contrassegno di incremento automatico nel file di configurazione xml di hazelcast. Quando l'ho spento, vedo multiple eccezioni nella mia istanza del server che lamentano il fatto che la porta non sia aperta (già in uso) per la porta 5701 (dal momento che il nocciolo non si sposta più sulla porta 5702 ecc.). Perché Hazelcast ha bisogno di questa proprietà quando sto utilizzando l'installazione del server abilitata per TCP?

compaiono i seguenti nelle mie dichiarazioni di registro dopo l'esecuzione il server e sembra di essere essere in ascolto sulla porta 5701 (impostazione predefinita in config):

Members [1] { 
     Member [127.0.0.1]:5701 this 
} 

2014-09-05 05:46:00,407 INFO c.h.c.LifecycleService [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 c.a.c.n.SendServerEmail [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 c.h.p.InternalPartitionService [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 c.h.i.DefaultAddressPicker [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 c.h.i.DefaultAddressPicker [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 c.h.system [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 c.h.system [main] [127.0.0.1]:5702 [dev] [3.2.4] Copyright (C) 2008-2014 Hazelcast.com 
2014-09-05 05:46:01,604 INFO c.h.i.Node [main] [127.0.0.1]:5702 [dev] [3.2.4] Creating TcpIpJoiner 
2014-09-05 05:46:01,606 INFO c.h.c.LifecycleService [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 c.h.c.TcpIpJoiner [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 c.h.c.TcpIpJoiner [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 c.h.n.SocketConnector [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 c.h.n.SocketConnector [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 c.h.n.SocketConnector [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 c.h.n.SocketAcceptor [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 c.h.n.TcpIpConnectionManager [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 c.h.n.TcpIpConnectionManager [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 c.h.c.TcpIpJoiner [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 c.h.c.TcpIpJoiner [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 c.h.c.TcpIpJoiner [main] [127.0.0.1]:5702 [dev] [3.2.4] Rebooting after 10 seconds. 
2014-09-05 05:46:48,639 INFO c.h.c.TcpIpJoiner [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 c.h.n.SocketConnector [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 c.h.n.SocketConnector [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 c.h.c.TcpIpJoiner [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 c.h.c.TcpIpJoiner [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 c.h.c.TcpIpJoiner [main] [127.0.0.1]:5702 [dev] [3.2.4] Rebooting after 10 seconds. 
2014-09-05 05:47:24,649 INFO c.h.c.TcpIpJoiner [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 c.h.c.TcpIpJoiner [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 c.h.n.SocketConnector [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 c.h.n.SocketConnector [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] 

Answer 1

server di Hazelcast cerchi di associare sulla porta specificata in la proprietà del porto. Se la porta predefinita non è disponibile per il binding, Hazelcast dovrebbe incrementare il numero di porta (usando il flag port count) fino a quando non ottiene una porta libera su cui eseguire il binding. Salvo errore, potrebbe tentare di eseguire il binding su tre porte o una per impostazione predefinita: controllerà e aggiornerà di conseguenza. È possibile impostare l'incremento automatico della porta su falso se si desidera che il server Hazelcast si leghi semplicemente su una porta e non incrementi.

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

Inoltre, assicurarsi che la porta 5701 non è in uso da un altro processo ed è disponibile per legare su e che non c'è niente sul sistema di prevenzione di un server di legare su quella porta, come qualsiasi firewall, ecc