Couchbase Server CPU Usage (beam.smp) in clustered environment

I do have a two node test-cluster running Couchbase community edition and after a few days the CPU usage (only of the second node) dramatically increases for a few hours and then drops down again. I’ve tried:

  • to delete the cluster and set it up again
  • to run it on different servers
    but the problems keeps reoccurring

The cluster (as it’s test only) does store very little data volume (Data/Disk Usage 173MB / 191MB and 5902 documents)

The high CPU usage is mainly caused by the beam.smp process:

I’m running the following version: 4.0.0-4051 Community Edition (build-4051)

Is there any way to find out what’s causing this high CPU usage and maybe a way to resolve this?


beam.smp is responsible for monitoring and managing all other underlying server processes such as ongoing XDCR replications, cluster operations, and views. You can read more about beam.smp here:

Do you have view/XDCR running in the cluster?
Also, may I ask how many cores do you have for the each machine?

Previously, we did see something like this in 2.5:
But this issue should be resolved now.


@peda can you describe your cluster in greater detail so we can get an idea how it is setup (n1ql, 2i, xdcr,…) thanks!

Oh, and great to see austrian fellows on the forums here :slight_smile:

First of all thanks for your quick replies.

There is no XDCR but there is 1 view document with 9 views and 1 index for N1QL. But none of the views is particularly complex - they are more like secondary indexes which do emit just hand full of fields.

Even though I’m aware that at least 4 cores are recommended these machines are only dual-core but that shouldn’t be any issue if there is very little load on the system, right?

The machines do have 30 GB of ram whereby 14336 MB are allocated for data and 2048 MB for index. So there should be enough spare RAM for the other processes.

@daschl the cluster is rather simple:
A simple 2 node cluster in the OVH Public Cloud with SP-30 instances (I know 3 nodes are recommended but for testing I decided to use 2 nodes)
Both servers are synchronizing their system time with an NTP server.
I’m using a private network (OVH vRack with the IP range)
There is no packet loss on the network connection - the ping is stable and between 0.5 and 2.5 ms
Servers are configured using host names - DNS resolution time shouldn’t be an issue either because I’ve added all host names and IP addresses to the /etc/hosts file
The application accessing Couchbase is situated in the same vRack (so no big delays their either)
Both servers are running all services (Data, Index, Query) and yes, I’m also using N1QL
In case you have any additional questions I’m happy to answer them :slight_smile:

If needed I can also provide log files

I’ve updated to Couchbase Community 4.1 (which was released yesterday) - so far the CPU usage looks much better - I’ll keep an eye on it over the next few days and let you know. As you can see in the screenshot of my original post it was also working fine with 4.0 for a few days.

How about now? The problem was resolved?

It at least didn’t happen again - so I think we can consider it to be resolved for now :slight_smile: