New to KubeDB? Please start here.

Neo4j Horizontal Scaling Overview

This page explains how KubeDB Ops-manager performs horizontal scaling for Neo4j using Neo4jOpsRequest.

Before You Begin

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

How Horizontal Scaling Works

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

The horizontal scaling process consists of the following steps:

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

1. Validates the requested server count in spec.horizontalScaling.server.
2. Pauses conflicting reconciliations for safe scale execution.
3. Updates the target Neo4j server replica count.
4. Applies reallocation policy from spec.horizontalScaling.reallocate.
5. Waits for members and database hosting to reach a healthy state.
6. Marks the operation Successful and resumes normal reconciliation.

Use Cypher views to verify topology and allocation after scaling:

• SHOW DATABASE <name> for allocation status.
• SHOW SERVERS for hosting distribution.

Next Step

Follow the detailed guide: Scale Neo4j Horizontally.