Aerospike: Up and Running

Chapter 7. Administration, Tools, and Configuration

Now that you’re ready to bring an Aerospike cluster online, you need to know how to keep the system online and deal with changes. You should understand the processes used to interact with the server so that you can manage it as part of your production environment. You will need to know how to cluster servers together, tune parameters, and manage user access. This chapter focuses on these essential aspects of administering Aerospike, exploring the tools and configurations to manage your Aerospike clusters.

Configuration

With your Aerospike installation, a configuration file should have been created at /etc/aerospike/aerospike.conf. This is the main configuration file and is only read when the Aerospike daemon is started. The format of this file does not adhere to any specific configuration formats such as YAML, JSON, or even INI. The format is proprietary and specific to Aerospike, though it resembles JSON.

Anatomy of a Config File

The Aerospike config file is divided into various sections known as contexts and subcontexts. Comments in the config file can be added by prepending the # symbol. You can use the Aerospike configuration reference to determine what each parameter does, review additional notes, and see properties of that configuration parameter, which will be discussed soon.

Note

We strongly recommend that you bookmark the Aerospike configuration reference. It’s an invaluable resource for interpreting the book and ...