New to KubeDB? Please start here.

Neo4j Vertical Scaling Overview

This page explains how KubeDB Ops-manager updates Neo4j pod resources using Neo4jOpsRequest.

Before You Begin

• You should be familiar with Neo4j.
• You should be familiar with Neo4jOpsRequest.

How Vertical Scaling Works

The following diagram shows how KubeDB Ops-manager performs vertical scaling for a Neo4j database. Open the image in a new tab to see the enlarged version.

The vertical scaling process consists of the following steps:

For a Neo4jOpsRequest with spec.type: VerticalScaling, KubeDB Ops-manager:

1. Validates CPU/memory values from spec.verticalScaling.server.resources.
2. Pauses conflicting reconciliations.
3. Applies updated requests/limits to Neo4j server pods.
4. Performs controlled restarts where necessary.
5. Waits for pods to become healthy with new resources.
6. Marks the request Successful after reconciliation.

Next Step

Follow the detailed guide: Scale Neo4j Vertically.