Euler2.0 大规模图数据加载时报错
- Dominant language
- C++
- Stars
- 2.9k
- Forks
- 553
- PR merge metrics
- No merged PRs in 30d
Description
在安装好zookeeper集群的基础上
调用代码:
euler.start(
directory='euler_graph_data_dir', # 图数据路径
shard_idx=k, # 当前启动的进程为k号shard
shard_num=N, # 一共有N个shard
zk_addr=zk_addr, # Zookeeper address, ip:port
zk_path=zk_path, # Zookeeper path
module=euler.Module.DEFAULT_MODULE)
while True:
time.sleep(1)
报错信息:
2020-08-16 17:09:50.725018: W /Euler-OpenSource/euler/core/graph/graph_builder.cc:156] Graph build completely!
2020-08-16 17:09:50.725038: W /Euler-OpenSource/euler/core/graph/graph.cc:111] Build graph successfully, shard Index: 2,
shard number: 3, data path: /home/cora/euler, sampler_type: node
2020-08-16 17:09:50.725307: W /Euler-OpenSource/euler/service/grpc_server.cc:166] Missing Index directory, skip loading index.
2020-08-16 17:09:50.725340: E /Euler-OpenSource/euler/core/graph/graph.cc:434] global sampler is not ok
2020-08-16 17:09:50.725355: F /Euler-OpenSource/euler/core/graph/graph_meta.cc:41] Find feature error, Unknown feature name: binary_graph_label
2020-08-16 17:10:30.745360: F /Euler-OpenSource/euler/common/zk_server_register.cc:83] ZK error when creating root node: operation timeout.
2020-08-16 17:11:10.769324: F /Euler-OpenSource/euler/common/zk_server_register.cc:106] ZK error when creating meta: operation timeout.
Segmentation fault
这是怎么产生的,怎样解决这个问题?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the logged locations core/graph/graph_meta.cc:41 and common/zk_server_register.cc:83,106, then review the graph data, feature metadata, index directory, and Zookeeper settings used by the shown euler.start call. Reproduce the three-shard load and determine why binary_graph_label is missing and why Zookeeper operations time out; done means the graph loads without those errors or a documented root cause is established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- Domain
- data, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100