Mesh Configuration


#1

Post by jmgomez » Tue Jun 24, 2014 8:22 am

I’m trying to configure a cluster using mesh.

The node1 ip is: 172.31.12.161 The node2 ip is: 172.31.12.160

I use ping command to probe the visibility between nodes and everithings is correct. The node1 configuration is:

heartbeat { mode mesh address 172.31.12.161 #It own ip port 3002 mesh-port 3002 mesh-address 172.31.12.160 #The Node2 IP interval 250 timeout 50 }

I execute sudo service aerospike start and everything is OK but I think the service is down because the port isn’t in use. To ensure it I probe the command “telnet localhost 3002” and I see “telnet: Unable to connect to remote host: Connection refused”

The second node config is: heartbeat { mode mesh address 172.31.12.161 #The Node1 IP port 3002 mesh-port 3002 mesh-address 172.31.12.161 #The Node1 IP interval 250 timeout 50 }

I execute sudo service aerospike start and the log show : Jun 24 2014 14:49:38 GMT: INFO (hb): (fabric/hb.c::1822) initializing mesh heartbeat socket : 172.31.12.161:3002 Jun 24 2014 14:49:38 GMT: WARNING (cf:socket): (socket.c::215) bind: Cannot assign requested address Jun 24 2014 14:49:38 GMT: CRITICAL PROCESS (as): (fabric/hb.c:as_hb_init_socket:1828) couldn’t initialize unicast heartbeat socket: Cannot assign requested address

Somebody can help me.

Thank


#2

Hi,

On both configurations, address needs to be the IP address for a local interface as described on: http://aerospike.com/docs/operations/configure/network/heartbeat/#mesh-unicast-heartbeat

For your second configuration, the address parameter should be 172.31.12.160.