Rohith Sampgod
04/06/2023, 10:16 AMstoraged
host based nebula graph cluster deployment, which has a large amount of data.
As per the documentation: https://docs.nebula-graph.io/3.4.1/5.configurations-and-logs/1.configurations/4.storage-config/#storage_configurations_for_large_dataset
I have set enable_partitioned_index_filter=true
in every storage nodes nebula-storaged.conf
.
Although 2 hosts use low amount RAM (expected behavior), the third host overloads the RAM and crashes.
Please suggest if there is anything missing to get the cluster working with low RAM allocations.阳子
04/07/2023, 2:27 AMRohith Sampgod
04/07/2023, 4:14 AM+--------------+------+-----------+----------+--------------+---------------------+------------------------+---------+
| Host | Port | HTTP port | Status | Leader count | Leader distribution | Partition distribution | Version |
+--------------+------+-----------+----------+--------------+---------------------+------------------------+---------+
| "10.0.1.8" | 9779 | 19779 | "ONLINE" | 33 | "MDB:33" | "MDB:33" | "3.3.0" |
| "10.0.1.95" | 9779 | 19779 | "ONLINE" | 33 | "MDB:33" | "MDB:33" | "3.3.0" |
| "10.0.1.252" | 9779 | 19779 | "ONLINE" | 34 | "MDB:34" | "MDB:34" | "3.3.0" |
+--------------+------+-----------+----------+--------------+---------------------+------------------------+---------+
Vertex and Edge Counts:
| "Space" | "vertices" | 4360152 |
| "Space" | "edges" | 195535793 |
Disk usage is around 50G each across hosts.
RAM usage shoots over 250Gb.阳子
04/07/2023, 6:53 AMRohith Sampgod
04/07/2023, 7:17 AMenable_partitioned_index_filter=true
will reduce the RAM requirement, which performing as expected in 2 hosts of the cluster (Max. RAM usage: 10-12gb), but the host with Leader Count 34
tries to use more than 250Gb.