Why is the aerospike cluster config is not working

Hi,

I’m trying to setup aerospike cluster of 3 nodes.I set this up by referring here.

Ip config of three nodes are - aerospike1 ip - 192.168.10.25 aerospike2 ip - 192.168.10.25 aerospike3 ip - 192.168.10.25

aerospike1 heartbeat config -

        heartbeat {
                mode mesh
                port 3002
                address 192.168.10.25

                mesh-seed-address-port 192.168.10.25 3002 
                mesh-seed-address-port 192.168.10.26 3002
                mesh-seed-address-port 192.168.10.27 3002

                interval 150
                timeout 10
        }

aerospike2 heartbeat config -

        heartbeat {
                mode mesh
                port 3002
                address 192.168.10.26

                mesh-seed-address-port 192.168.10.25 3002 
                mesh-seed-address-port 192.168.10.26 3002
                mesh-seed-address-port 192.168.10.27 3002

                interval 150
                timeout 10
        }

aerospike3 heartbeat config -

        heartbeat {
                mode mesh
                port 3002
                address 192.168.10.27

                mesh-seed-address-port 192.168.10.25 3002 
                mesh-seed-address-port 192.168.10.26 3002
                mesh-seed-address-port 192.168.10.27 3002

                interval 150
                timeout 10
        }

The complete configuration is in github here.

When I start the aerospike service it is working fine in all the nodes. But when I do aql command only on aerospike1 it is working but not on aerospike2 and aerospike3.

The error I’m getting in amc is -

When I start the aerospike service it is working fine in all the nodes.

Can you please share the server version and what you did to confirm the server was running fine on all nodes? You may want to check if there are no errors in the log and that the server came up successfully.

The fact that AQL does not run on two nodes and these nodes show up with the cluster integrity error probably means the cluster is not formed. The log should point to the underlying issue.

Also cross-posted on StackOverflow… setting up aerospike cluster of 3 nodes - Stack Overflow