Doubts with replicas


#1

Hi, i have some doubts… In this moment i have 3 servers with the same features. I have the replication factor in 2 ( i underestand that this mean that have two replicas, the server and the replica) i wanna to have 3 replicas but when i made this change the server don´t start… this is my configuration:

**> # Aerospike database configuration file.

This stanza must come first.

service { user root group root paxos-single-replica-limit 1 # Number of nodes where the replica count is automatically reduced to 1. pidfile /var/run/aerospike/asd.pid service-threads 4 transaction-queues 4 transaction-threads-per-queue 4 proto-fd-max 15000 paxos-protocol v4 } logging { # Log file must be an absolute path. file /var/log/aerospike/aerospike.log { context any info } } network { service { address any port 3000 } heartbeat { mode mesh address 10.99.0.12 port 3002 mesh-seed-address-port 10.99.0.11 3002 mesh-seed-address-port 10.99.0.10 3002 interval 150 timeout 20 # To use unicast-mesh heartbeats, comment out the 3 lines above and # use the following 4 lines instead.

mode mesh

port 3002

mesh-address 10.1.1.1

mesh-port 3002

            interval 150
            timeout 10
    }
    fabric {
            port 3001
    }
    info {
            port 3003
    }

} #namespace test {

replication-factor 2

memory-size 4G

default-ttl 30d # 30 days, use 0 to never expire/evict.

storage-engine memory

#} namespace databases { replication-factor 2 memory-size 4G default-ttl 30d # 30 days, use 0 to never expire/evict. storage-engine memory # To use file storage backing, comment out the line above and use the # following lines instead. storage-engine device { file /opt/aerospike/data/databases.dat filesize 1G data-in-memory true # Store data in memory in addition to file. } } cluster { mode dynamic self-group-id 201 }**


#2

Hi,

  1. Looking at your configuration you have added the mesh configuration twice. This will not work. See more about network configuration using mesh here: http://www.aerospike.com/docs/operations/configure/network/heartbeat/

  2. You have added rackware (By defining cluster) with only three nodes? Read more about rackaware here: http://www.aerospike.com/docs/operations/configure/network/rack-aware/

You might want to start with a very simple configuration and then add one thing at a time and make sure the server starts each time.

Thanks Petter


#3

Hi Petter, thanks for your help,

  1. That was a mistake when i write the configuration, when i copy it, the # symbols disappear and the mesh configuration seems to be twice, but the mesh configuration is really only one time in the file.

  2. So… When i configure a cluster that means that i configure rack aware too? I see in the documentation of rack awareness an example in that a group is configured with two nodes, so why its a problem the configuration with three?


#4

You don’t need the “cluster” section at all.

The network / heartbeat section already defines the other node to talk to for creating the cluster of nodes.