Hello Albot,
Now I am trying to add new machine(10.84.245.153) with the existing cluster. Below is the configuration file of new node.
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
log-local-time true
}
logging {
# Log file must be an absolute path.
file /var/log/aerospike/aerospike.log {
context any debug
}
}
network {
service {
address any
port 3000
access-address 10.84.245.153
}
heartbeat {
mode mesh
port 3002
# To use unicast-mesh heartbeats, remove the 3 lines above, and see
# aerospike_mesh.conf for alternative.
mesh-seed-address-port 172.20.21.185 3002
mesh-seed-address-port 172.20.21.186 3002
mesh-seed-address-port 172.20.21.187 3002
mesh-seed-address-port 172.20.21.188 3002
mesh-seed-address-port 172.20.21.192 3002
interval 150
timeout 10
}
fabric {
port 3001
}
info {
port 3003
}
}
namespace test {
replication-factor 2
memory-size 4G
default-ttl 30d # 30 days, use 0 to never expire/evict.
storage-engine memory
}
namespace bar {
replication-factor 2
memory-size 4G
default-ttl 30d # 30 days, use 0 to never expire/evict.
storage-engine memory
# To use file storage backing, comment out the line above and use the
# following lines instead.
# storage-engine device {
# file /opt/aerospike/data/bar.dat
# filesize 16G
# data-in-memory true # Store data in memory in addition to file.
# }
}
namespace lgp {
replication-factor 2
memory-size 10G
default-ttl 0 # 5 days, use 0 to never expire/evict.
high-water-memory-pct 90 # How full may the memory become before the server begins eviction (expiring records early)
high-water-disk-pct 80 # How full may the disk become before the server begins eviction (expiring records early)
stop-writes-pct 90 # How full may the memory become before we disallow new writes
# storage-engine memory
# To use file storage backing, comment out the line above and use the
# following lines instead.
storage-engine device {
file /myntra/aerospike/data/lgp/object.dat
filesize 750G
# data-in-memory true # Store data in memory in addition to file.
}
}
namespace lgp_cache {
replication-factor 1
memory-size 10G
default-ttl 2d # 5 days, use 0 to never expire/evict.
high-water-memory-pct 60 # How full may the memory become before the server begins eviction (expiring records early)
# high-water-disk-pct 80 # How full may the disk become before the server begins eviction (expiring records early)
stop-writes-pct 90 # How full may the memory become before we disallow new writes
storage-engine memory
}
Configuration file from one of the node from existing cluster is given below.
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
log-local-time true
}
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 172.20.21.185
}
heartbeat {
mode mesh
port 3002
# To use unicast-mesh heartbeats, remove the 3 lines above, and see
# aerospike_mesh.conf for alternative.
mesh-seed-address-port 172.20.21.186 3002
mesh-seed-address-port 172.20.21.187 3002
mesh-seed-address-port 172.20.21.188 3002
mesh-seed-address-port 172.20.21.192 3002
interval 150
timeout 10
}
fabric {
port 3001
}
info {
port 3003
}
}
namespace test {
replication-factor 2
memory-size 4G
default-ttl 30d # 30 days, use 0 to never expire/evict.
storage-engine memory
}
namespace bar {
replication-factor 2
memory-size 4G
default-ttl 30d # 30 days, use 0 to never expire/evict.
storage-engine memory
# To use file storage backing, comment out the line above and use the
# following lines instead.
# storage-engine device {
# file /opt/aerospike/data/bar.dat
# filesize 16G
# data-in-memory true # Store data in memory in addition to file.
# }
}
namespace lgp {
replication-factor 2
memory-size 10G
default-ttl 0 # 5 days, use 0 to never expire/evict.
high-water-memory-pct 90 # How full may the memory become before the server begins eviction (expiring records early)
high-water-disk-pct 80 # How full may the disk become before the server begins eviction (expiring records early)
stop-writes-pct 90 # How full may the memory become before we disallow new writes
# storage-engine memory
# To use file storage backing, comment out the line above and use the
# following lines instead.
storage-engine device {
file /opt/aerospike/data/lgp/object.dat
filesize 150G
# data-in-memory true # Store data in memory in addition to file.
}
}
namespace lgp_cache {
replication-factor 1
memory-size 15G
default-ttl 2d # 5 days, use 0 to never expire/evict.
high-water-memory-pct 60 # How full may the memory become before the server begins eviction (expiring records early)
# high-water-disk-pct 80 # How full may the disk become before the server begins eviction (expiring records early)
stop-writes-pct 90 # How full may the memory become before we disallow new writes
storage-engine memory
}
Only difference between these 2 files is size of filesize(for lgp namespace) and memory-size(for lgp_cache) but new machine is not getting added in the existing cluster.
Output of existing cluster
Admin> info network
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Network Information~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Node Node Ip Build Cluster Cluster Cluster Principal Client Uptime
. Id . . Size Key Integrity . Conns .
172.20.21.185:3000 BB92E0FBD565000 172.20.21.185:3000 C-3.9.1 5 48CC27E9791254A3 True BB9EF48BD565000 32 3481:48:04
172.20.21.186:3000 BB99214BD565000 172.20.21.186:3000 C-3.9.1 5 48CC27E9791254A3 True BB9EF48BD565000 33 3481:45:12
172.20.21.187:3000 *BB9EF48BD565000 172.20.21.187:3000 C-3.9.1 5 48CC27E9791254A3 True BB9EF48BD565000 30 3481:43:31
172.20.21.188:3000 BB94179BD565000 172.20.21.188:3000 C-3.9.1 5 48CC27E9791254A3 True BB9EF48BD565000 33 3481:12:53
172.20.21.192:3000 BB9245FBD565000 172.20.21.192:3000 C-3.9.1 5 48CC27E9791254A3 True BB9EF48BD565000 31 3500:25:01
Number of rows: 5
output of new machine
Admin> info network
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Network Information~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Node Node Ip Build Cluster Cluster Cluster Principal Client Uptime
. Id . . Size Key Integrity . Conns .
myntra-none-6046925:3000 *BB999F5540A0102 10.84.245.153:3000 C-3.9.1 1 CC413304FC829C72 True BB9EF48BD565000 7 00:23:22
Number of rows: 1
I am not able to figure it out why this new machine is not able to join existing cluster. Basic check(like accessibility of machines, port open) has been done.
Can you please help me to debug this issue. Any lead would be helpful.
