What does Neo4j do in the spare time?

I have a cluster consisting of 3 nodes of Neo4j 3.5. We are not in the production yet so for the vast majority of the time this cluster does nothing i.e. there are no writes and barely any reads.

Despite this fact when I look at JVM Heap Size I observe something suspicious (for each node):

  1. The heap size increases until it reaches the limit.
  2. Then it drops almost to 0.
  3. Then it increases until it reaches the limit.
  4. Then it drops almost to 0.
  5. ... and so on.

In one case, the cycle takes more than 1 hour. I also checked another cluster and the situation is similar but with some differences: the cycle is much shorter and the heap size does not drop to 0.

My questions are:

  1. Is it a normal situation? Should I worry?
  2. If it is normal, what is the reason behind that. What does Neo4j actually do?
  3. Why do sometimes the cycle described above takes X minutes and in another case Y minutes?

Michał Komorowski

Most likely it's the health checks of the cluster members that they have to do to ensure proper operations of the cluster, see

The different cycles are perhaps due to heap sizes.

1 Like