Hi, so we have just upgraded to 3.10 and upon restarting both servers for some reason they no longer talk to each other. Before ripping apart the networks I wanted to just check that the config changes from old to new are correct. This was our previous working configuration:
# Aerospike database configuration file.
service {
user root
group root
paxos-single-replica-limit 1 # Number of nodes where the replica count is automatically reduced to 1.
pidfile /var/run/aerospike/asd.pid
service-threads 4
transaction-queues 4
transaction-threads-per-queue 4
proto-fd-max 15000
}
logging {
# Log file must be an absolute path.
file /var/log/aerospike/aerospike.log {
context any info
}
}
network {
service {
address any
port 3000
access-address 192.168.120.52
}
heartbeat {
mode multicast
address 239.1.99.51
port 9918
interface-address 192.168.60.52
interval 150
timeout 10
}
fabric {
address any
port 3001
}
info {
address any
port 3003
}
}
namespace temp01 {
replication-factor 2
memory-size 8G
default-ttl 0
storage-engine device {
device /dev/sdb1
scheduler-mode noop
write-block-size 128K
}
}
namespace adspruce {
replication-factor 2
memory-size 98G
default-ttl 0
storage-engine device {
device /dev/sdc1
device /dev/sdd1
device /dev/sde1
device /dev/sdf1
scheduler-mode noop
write-block-size 128K
}
}
and this is our new one. The configs are identical apart from the IP addresses which would be expected (right?) By this I mean we have 2 servers both running the same config, but with the IP’s being .51 and .52
# Aerospike database configuration file.
service {
user root
group root
paxos-single-replica-limit 1 # Number of nodes where the replica count is automatically reduced to 1.
pidfile /var/run/aerospike/asd.pid
service-threads 4
transaction-queues 4
transaction-threads-per-queue 4
proto-fd-max 15000
}
logging {
# Log file must be an absolute path.
file /var/log/aerospike/aerospike.log {
context any info
}
}
network {
service {
address any
port 3000
access-address 192.168.120.51
}
heartbeat {
mode multicast
multicast-group 239.1.99.51
port 9918
address 192.168.60.51
interval 150
timeout 10
}
fabric {
address 192.168.60.51
port 3001
}
info {
address any
port 3003
}
}
namespace temp01 {
replication-factor 2
memory-size 8G
default-ttl 86400 # 86400 = 24 hours
storage-engine device {
device /dev/sdb1
scheduler-mode noop
write-block-size 128K
}
}
namespace adspruce {
replication-factor 2
memory-size 98G
default-ttl 0 # 0 = no default TTL
storage-engine device {
device /dev/sdc1
device /dev/sdd1
device /dev/sde1
device /dev/sdf1
scheduler-mode noop
write-block-size 128K
}
}
Any thoughts on why this may be happening?
