Aerospike Config for small server

I would like to know what is the ideal configuration of the Aerospike namespace for a mini (staging) server on Ubuntu 12.04 with 1GB RAM and 1GHz CPU

Some requirements: 1. I want to permanently store data on disk (not using it as a cache). 2. I only use one node 3. I don't want to limit the size of my data files.

Here is my current configuration snippet that I am using:

namespace default {
        replication-factor 1
        memory-size 1G
        default-ttl 0 # not sure if this is for cache or disk

        storage-engine device {
                file /opt/aerospike/data/default.dat
                filesize 2T
                data-in-memory true
        }
}

      

thank

+3


source to share


1 answer


  • Aerospike does not cache data-in-memory . If the parameter is data-in-memory

    set to true, all of your data must go into RAM.
  • On one node, you won't be influencing the parameter replication-factor

    .
  • Aerospike has a limit of 2 TiB per file , but you can create multiple files of that size and Aerospike will distribute data over them. When navigating through the file system, multiple files often help. Also, if you are going to use a filesystem, then you might want to look into disabling atime when setting up disks.
  • default-ttl - how long the server will keep the recording after it is recorded by default (can be overridden by your application). The default is ttl 0 which means never expire or evict data.

Example configuration with multiple files:



namespace default {
        replication-factor 1
        memory-size 1G
        default-ttl 0 # (This applies to the primary index)

        storage-engine device {
                file /opt/aerospike/data/file0.dat
                file /opt/aerospike/data/file1.dat
                file /opt/aerospike/data/file2.dat
                file /opt/aerospike/data/file3.dat
                file /opt/aerospike/data/file4.dat
                file /opt/aerospike/data/file5.dat
                filesize 2T
                data-in-memory true
        }
}

      

+3


source







All Articles