Thank you very much for the additional information. I’m sorry to hear that you had to move on to a different database.
From the kernel version (
4.4.0-042stab127.2) in the
uname output it seems that Strato configure and build their own Linux kernels for use with their virtual servers, i.e., this isn’t a standard Ubuntu kernel. It looks like their kernel is pretty stripped down. They didn’t only remove the hot-plugging support, but a lot more: the
/sys/devices/system/cpu/cpu0 directory is completely empty on your server, for example.
On startup, Aerospike gathers information about the CPU and memory configuration of the machine it runs on. This mechanism depends on the information provided by the kernel under
/sys/devices/system/cpu. Unfortunately, all of this has been stripped away by Strato when they configured their custom kernel.
The Strato V40 is a para-virtualized machine (Virtuozzo). This means that the virtual servers (guests) share the Linux kernel of the underlying physical server (host). That’s why you didn’t find any packages named
linux-image on your virtual server - your guest doesn’t have a kernel installed, because it uses the host’s kernel. Unfortunately, this also means that you cannot change the kernel, e.g., to a standard Ubuntu kernel. You’re stuck with the (host) kernel provided by Strato.
So, I’m afraid that it will be difficult to get Aerospike to work with a V40. I have opened an internal ticket, so that we’ll look into this, but the fix is non-trivial, I’m afraid. It would require a substantial rework of the performance optimization code that adapts Aerospike’s as well as the kernel’s configuration to the hardware it runs on, things like the number and topology of CPUs and NUMA nodes, NIC queues, etc.
Sorry that I do not have better news for you.