Skip to content
This repository has been archived by the owner on Dec 1, 2022. It is now read-only.

[bug] something crashed #871

Closed
whitewum opened this issue Mar 24, 2021 · 4 comments
Closed

[bug] something crashed #871

whitewum opened this issue Mar 24, 2021 · 4 comments
Assignees
Labels
bug Type: something is unexpected

Comments

@whitewum
Copy link
Contributor

image

image

match (s)-[:relation*1..3]-(e) where id(s) == 1 RETURN count (distinct id(e))

there are only 200 nodes, and they are fully directed connected pairwise. but this query takes too many memory.

You can reproduce this case very easy.

[1330702.883214] Out of memory: Kill process 9695 (nebula-graphd) score 926 or sacrifice child
[1330702.883350] Killed process 9695 (nebula-graphd) total-vm:22125060kB, anon-rss:15918864kB, file-rss:0kB, shmem-rss:0kB
[1330703.599318] oom_reaper: reaped process 9695 (nebula-graphd), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB
free -m
              total        used        free      shared  buff/cache   available
Mem:          16039         303       15517           0         218       15460
Swap:          4095         431        3664
@whitewum
Copy link
Contributor Author

image
Uploading image.png…

@whitewum
Copy link
Contributor Author

is it reasonable for a 200 nodes network?

@whitewum
Copy link
Contributor Author

besides, why memory is not released after query is over.

image

@Aiee Aiee added the bug Type: something is unexpected label Apr 20, 2021
@CPWstatic
Copy link
Contributor

Suppose to be OOM.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Type: something is unexpected
Projects
None yet
Development

No branches or pull requests

4 participants