-
Notifications
You must be signed in to change notification settings - Fork 32
Nebula Algorithm #91
Comments
The first half of the job is to read data from Nebula, and then algorithm will be executed. It's strange that mapPartitions lasts 35 minutes. How many records of edge callTO ? Please post the result of If your algorithm's result will be write back to Nebula, please package nebula-algorithm with branch |
yes, I use nebula-algorithm with branch master |
You has 682 million edges, and your job was submit using local mode. You can check the log, maybe there's some OOM error. Please use yarn mode to submit your spark job, and config more memory for executor and driver. |
Will close it as it's been inactive for days. Feel free to reopen it. |
Nebula Graph 2.0.0
Deployment type (Single-Host)
Hardware info
Disk in use (HDD)
CPU: Intel(R) Xeon(R) CPU E5-2630 v2 @ 2.60GHz * 10
Ram: 64 G
+----+------------------+------------------+----------------+---------+------------+--------------------+-------------+-----------+ | ID | Name | Partition Number | Replica Factor | Charset | Collate | Vid Type | Atomic Edge | Group | +----+------------------+------------------+----------------+---------+------------+--------------------+-------------+-----------+ | 1 | "CallConnection" | 10 | 1 | "utf8" | "utf8_bin" | "FIXED_STRING(80)" | "false" | "default" | +----+------------------+------------------+----------------+---------+------------+--------------------+-------------+-----------+
I wanna use pagerank algorithm. I use below configuration:
after about several minutes and use all CPU but not RAM,
here is the spark UI
after some minutes,
just do nothing and all task gone!
The text was updated successfully, but these errors were encountered: