How to add a namespace in a production cluster

We have a production environment with many Aerospike nodes. Now we need to add a new namespace to that cluster, so we changed all the configuration files, but we yet have to restart the servers so the change take place.

Which is the best way to apply the config change (with the new namespace) and keeping the whole cluster active without interfering with production operations? Is there a way to restart one by one?


Currently you cannot add a namespace without a cluster wide restart.

Hello kporter, thanks for your answer!

Then how do you add a namespace in your cluster without downtime? Is that possible?


There isn’t a way to add a namespace without downtime at this time.

1 Like

Is this a feature that you are currently working on, and if so, do you have a time frame on when the feature will be completed?

It isn’t a direct priority at the moment; however, we are currently working on many of the prerequisites required to roll in a new namespace.

So is there any way possible for me to effectively add a new namespace without users not being able to access the data during the process?

This question has already been answered in this thread.

so this post doesn’t hint at a solution to this at all?:

That solution is very involved and requires using an enterprise feature (XDR) and asbackup as well as being able to trigger your clients to “cut over to the new cluster”.

What I believe is being asked in this thread is the ability to add a namespace to an existing cluster without downtime. I assume this means either dynamically or through rolling restart were at most (replication factor - 1) nodes are down at any given instant. The latter is frequently discussed internally and many of the major obstacles for rolling in a namespace intersect with current feature development efforts.

The ability to add/remove namespaces with rolling restart of the cluster is added starting server version for both Community and Enterprise versions on paxos-protocol version v5.

[AER-3485] - (KVS) Support adding/removing namespaces with rolling restart.

@anushree. What does

Support adding/removing namespaces with rolling restart


Does it has to modify the aerospace.conf file and restart the cluster?

I do not see any API with namespace in the latest Java Client (4.0.2).

It means that you can add/remove a namespace in aerospike.conf and restart the cluster one node at a time (which means no downtime for existing namespaces).

Please do not dual post in the forums.

Sorry, but I am afraid that this may not be what this post expected: Create a new namespace dynamically, without restart. I thought we can dynamically add/remove namespaces instead of configuring it and restart the cluster, I think that is more attractive. Any plan for this feature? Thanks.

There aren’t any plans to make namespace addition/removal dynamic at this time.

© 2015 Copyright Aerospike, Inc. | All rights reserved. Creators of the Aerospike Database.