Hi All,
I have a 2 node cluster with the same server configuration as mentioned below :
service {
user root
group root
paxos-single-replica-limit 1
pidfile /var/run/aerospike/asd.pid
service-threads 4
transaction-queues 4
transaction-threads-per-queue 4
proto-fd-max 15000
nsup-period 1
}
logging {
file /ext/log/aerospike/aerospike.log {
context any warning
}
}
network {
service {
address any
port 3000
}
heartbeat {
mode mesh
port 3002
mesh-address 10.16.12.20
mesh-port 3002
interval 150
timeout 10
}
fabric {
port 3001
}
info {
port 3003
}
}
namespace testing {
replication-factor 2
memory-size 2G
default-ttl 365d
high-water-memory-pct 60
high-water-disk-pct 80
stop-writes-pct 90
storage-engine device {
device /dev/xvdh
scheduler-mode noop
write-block-size 128K
data-in-memory false
defrag-lwm-pct 50
defrag-startup-minimum 10
}
}
What we are trying to do is use the SSD for the data storage and we, for the time being, have a limited RAM to allocate, but as the policies dictate that the ram will be used for the indexing and it stops writes rather than evicting as the (memory_lwm >= index_sz) && (ssd_lwm >= data_sz) is not breached.
So, what I basically want to know is if it’s possible to have a config where the data eviction from the RAM can happen but not from the SSD and also not to have the insertions in the SSD to stop. (Pardon me if I am willing to have this weird config )
We have gone through the discussion about eviction and expiration policies on the link :
And also the reasons which contribute to the evictions.
I have went through the forum and also the documentation but i can’t find a way out. Can you guys guide me through my problem and help me out or help me understand what I can do.
Best Regards!