JanusGraph / JanusGraph/janusgraph
Janusgraph 0.5.3 potential memory leak
- Dominant language
- Java
- Stars
- 5.8k
- Forks
- 1.2k
- Avg merge
- 13h 53m
- Merged PRs (30d)
- 6
Description
As noted in discussion, this PR potentially could be the cause of OOM when used with CQL storage backend: https://github.com/JanusGraph/janusgraph/pull/2080
- Version: 0.5.3
- Storage Backend: cql
- Mixed Index Backend: none
- Link to discussed bug: https://lists.lfaidata.foundation/g/janusgraph-users/topic/80139368
- Expected Behavior: No OOM
- Current Behavior: OOM
- Steps to Reproduce: https://gist.github.com/mad/df729c6a27a7ed224820cdd27209bade
Contributor guide
Research direction
Start with pull request 2080, the linked discussion, and the reproduction gist for the CQL storage backend. Reproduce the OOM on JanusGraph 0.5.3, then trace the suspected change and confirm that the issue is resolved when the reproduction completes without exhausting memory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100