I am desperately trying to form a cluster with Aerospike 3.5.14 Community Edition. I have two LXC containers running on two different hosts. Aerospike is running on the LXC container. The containers are configured with a bridge and routing between the hosts and the containers are done using iptables nat rules.
aerospike1:
- container address : 192.168.11.12 (eth0); the address inside the container
- host address for the container : 192.168.16.131
aerospike2:
- container address 192.168.11.12 (eth0); the address inside the container
- host address for the container : 192.168.16.132
Here is the aerospike network configuration for aerospike1 :
network {
service {
address any
port 3000
access-address 192.168.16.131 virtual
network-interface-name eth0
}
heartbeat {
mode mesh
port 3002 # Heartbeat port for this node.
# List one or more other nodes, one ip-address & port per line:
mesh-seed-address-port 192.168.16.132 3002
interval 250
timeout 10
}
fabric {
port 3001
}
info {
port 3003
}
}
and here is the aerospike configuration for the second node :
network {
service {
address any
port 3000
access-address 192.168.16.132 virtual
network-interface-name eth0
}
heartbeat {
mode mesh
port 3002 # Heartbeat port for this node.
# List one or more other nodes, one ip-address & port per line:
mesh-seed-address-port 192.168.16.131 3002
interval 250
timeout 10
}
fabric {
port 3001
}
info {
port 3003
}
}
The cluster does not form and I have the following errors in the logs:
Jun 29 2015 11:50:42 GMT: INFO (paxos): (paxos.c::2367) Cluster Integrity Check: Detected succession list discrepancy between node bb97379253e1600 and self bb97279253e1600 Jun 29 2015 11:50:42 GMT: INFO (paxos): (paxos.c::2412) CLUSTER INTEGRITY FAULT. [Phase 1 of 2] To fix, issue this command across all nodes: dun:nodes=bb97379253e1600 Jun 29 2015 11:50:42 GMT: INFO (hb): (hb.c::2319) HB node bb97379253e1600 in different cluster - succession lists don’t match
I do not understand what is false in my setup.
Best regards, Christpohe Burki