Delete a Neo4j node
Delete DB Node removes a member and its managed database data. Retain verified backups and confirm application and host ownership before submitting.
Prepare the removal
Retain the required healthy primaries and voting quorum. The standard cluster requires at least three primaries. Review leadership and database topology before selecting a member for removal.
Record the project, selected host, roles and installed versions. Complete any required switchover and confirm the remaining members are healthy.
Delete the member
- Open Lifecycle → Delete DB Node.
- Select the exact member in Host Name.
- Check Selected Node Name.
- Enter the selected name in Confirm Node Name.
- Read and select the risk acknowledgment.
- Enter Remarks and choose Delete Now once.
- Follow Activity through member removal and cleanup.
Verify the result
Confirm the selected member is absent from the current topology and the remaining deployment has healthy leadership and replication. Check that the removed service is no longer running and monitoring reflects the retirement.
Do not release the server for reuse until cleanup is confirmed. Historical monitoring panels can retain earlier samples.
For a failed or partial removal, retain the first error and request details and contact support before retrying.