Installation steps

Gluesync NoSQL to NoSQL for Aerospike

Prerequisites

To have Gluesync working on your Aerospike instance you will need to have:

  • valid user credentials with permission of writing to the target database

Basic configuration example

This module can be customized by using a configuration file, in JSON format. The file name to use must be specified as a parameter when launching the app, with the -f or --file tokens. The file should be composed by the union of common configuration files (see here Installation steps) and source/destination specific configuration:

{
  ...
  "aerospike": {
    "certificatesPath": "/path/to/certs/dir/cert.crt",
    "certificatesPassword": "change_me",
    "timeoutSeconds": 60,
    "indexReplicaCount": 0,
    "disableAuth": false,
    "additionalHosts": ["IP_ADDRESS_HOST#1", "IP_ADDRESS_HOST#2", ...]
  },
}

Aerospike-specific configurations are listed under the aerospike property:

  • certificatesPath (optional): the path to the certificate that needs to be used when connecting to an Aerospike instance using a secure connection (TLS). If omitted, no certificate is used;

  • certificatesPassword (optional): if a certificate path is specified, then this value is passed as a keystore password;

  • timeoutSeconds (optional): number of seconds to set as timeout for operations involving communication with Aerospike. The default value is 60 seconds.;

  • disableAuth (optional), defaults to false: you can set that parameter to true to disable the authentication mechanism (as per the Aerospike docs) when you’re connecting to a development instance of Aerospike.

  • additionalHosts (optional), defaults to null: tells Aerospike target connector to make use of a cluster map of additional hosts available at the bootstrap time by feeding those to the Aerospike client SDK. If you don’t provide additional hosts at bootstrap time they will be then retrieved anyway when the connection to targetHost is established. This comes to help in case the targetHost is down at the bootstrap time.

Aerospike bin names and entity names

Aerospike identifies the bin object with a key name that uniquely identifies an object stored in the database.

Since each bin key has a maximum length of 14 characters Gluesync will throw an exception in case you accidentally have placed a longer entity name inside the sourceEntities list.