Aws instance R38XL compare with R3.2xl


#1

Hi,

I have dome many tests on R3.2xl which seem to be the recommended size. got good results. when i switched to r3.8xl i started to get a lot of memory issues. nothing help including raising the Ram limit to 20g.

any issue with using r3.8xl with Aerospike, is there a better configuration ?

Max


#2

I just want to add the exception i am getting – i though that memory is not an issue since it dump data into the flash ?

com.aerospike.client.AerospikeException: Error Code 8: Server memory error at com.aerospike.client.command.WriteCommand.parseResult(WriteCommand.java:59) at com.aerospike.client.command.SyncCommand.execute(SyncCommand.java:56) at com.aerospike.client.AerospikeClient.put(AerospikeClient.java:295) at com.emc.benchmark.clients.AerospikeDBClient.set(AerospikeDBClient.java:61) at com.emc.benchmark.clients.AerospikeDBClient.mSet(AerospikeDBClient.java:124) at com.emc.benchmark.BenchmarkRunner$1.run(BenchmarkRunner.java:176) at java.lang.Thread.run(Thread.java:745)


#3

hi Max,

Error Code 8 usually means the server is running out of configured memory for aerospike.

There are three broad ways of configuring a namespace storage

  1. In-memory only
  2. In-memory with disk storage
  3. Disk storage only

Irrespective of the storage method, you have to ensure that there is always enough memory configured and available for aerospike process. Aerospike will not flush excess data or index to disk when memory is full. It will evict the data/index as applicable but will not dump out to disk.

Please confirm that you are running with the default high-water-mark values and the nodes have enough free memory.

Please note this error is independent of r3.2xl and r3.8xl. You might have seen this in r3.8xl because you would have put in more number of objects. Did you update the aerospike config in r3.8xl to increase the memory configured in the namespace section?