The Aerospike Knowledge Base has moved to https://support.aerospike.com. Content on https://discuss.aerospike.com is being migrated to either https://support.aerospike.com or https://docs.aerospike.com. Maintenance on articles stored in this repository ceased on December 31st 2022 and this article may be stale. If you have any questions, please do not hesitate to raise a case via https://support.aerospike.com.
FAQ - Invalid namespace error.
Detail
Client got “Invalid namespace” error exception even though the namespace is correctly specified.
Caused by: com.aerospike.client.AerospikeException: Invalid namespace: bar
at com.aerospike.client.command.Command.getSequenceNode(Command.java:1052)
at com.aerospike.client.command.Command.getNode(Command.java:1032)
at com.aerospike.client.command.SyncCommand.execute(SyncCommand.java:60)
at com.aerospike.client.AerospikeClient.get(AerospikeClient.java:783)
at com.fbt.speed.dao.SpeedDao.getSpeedData(SpeedDao.java:46)
at com.fbt.speed.api.SpeedApi.getSpeedById(SpeedApi.java:41)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:508)
at com.ibm.ws.jaxrs20.server.LibertyJaxRsServerFactoryBean.performInvocation(LibertyJaxRsServerFactoryBean.java:651)
Answer
The error means the namespace is not found in the partition map (keyed by the specified namespace). Namespaces are statically configured on the server-side and never change while the server is running. When the AerospikeClient instance is constructed, the namespaces are retrieved from the servers.
So the client could be pointing to the a different cluster with no such namespace. It is also possible the access-address is not correctly configured.
One not common case that has been observed is one with an MTU mismatch in a docker environment.
After fixing the client MTU to match with the other instances the issue was resolved:
cat /etc/docker/daemon.json
{
"mtu" : 1400
}
In this case, the client also contained errors like these every second:
2018-10-30 19:02:54 WARN Node BB9AB1F9E565000 partition refresh failed: AEROSPIKE_ERR_TIMEOUT
2018-10-30 19:02:55 WARN Node BB9AB1F9E565000 partition refresh failed: AEROSPIKE_ERR_TIMEOUT
2018-10-30 19:02:56 WARN Node BB951619E565000 partition refresh failed: AEROSPIKE_ERR_TIMEOUT
This is an indication of a network issue. This can also be reproduced by dropping packets using special firewall rules in a non-docker environment. When the client gets a timeout error, it will return an “invalid namespace” because the namespace is not found in the current parition map.
Keywords
CLIENT INVALID NAMESPACE ERROR EXCEPTION MTU EXCEPTION
Timestamp
12/17/2018