Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Used memory hits the high watermark(0.800000) of total system memory. #5745

Closed
LETMECALM opened this issue Oct 29, 2023 · 9 comments
Closed
Labels
type/question Type: question about the product

Comments

@LETMECALM
Copy link

LETMECALM commented Oct 29, 2023

Question: Used memory hits the high watermark(0.800000) of total system memory.
版本:3.4,会出现周期性OOM问题,请问如何解决

@Nicole00
Copy link
Contributor

https://docs.nebula-graph.com.cn/3.6.0/5.configurations-and-logs/1.configurations/3.graph-config/#memory
可以修改 nebula-graphd.conf 里的这个配置,然后重启graphd
该值默认是 0.8 表示 80% ,可以改成 0.9999

@LETMECALM
Copy link
Author

LETMECALM commented Oct 30, 2023

updated by wey: translated into EN

The judgment condition for the threshold is available memory divided by (total memory - reserved memory). If the available memory is still below this threshold of 0.99, it should be lowered instead of raised. Adjusting the threshold seems to be a temporary solution rather than addressing the root cause. The exception occurs when executing the match query command, while other graph-related operations work fine. Does match operation consume system memory? By default, memory_purge_enabled = true enables regular memory cleanup. Why isn't the memory space being released? This issue occurs periodically and I would appreciate an explanation.


阈值的判断条件是 可用内存/(总内存 - 保留内存) ,改成 0.99 可用内存还是低于该阈值,应该是调低而不是调高吧,调阈值的方式应该是治标不治本吧。报该异常是进行 match query 命令是报错,其他图相关操作是正常的,match 操作会占用系统内存吗,默认开启了memory_purge_enabled = true 定期清理内存,为啥内存空间没有得到释放,这个问题是周期性出现的,望解答。

@wey-gu
Copy link
Contributor

wey-gu commented Oct 30, 2023

OOM

"Memory Tracker" was introduced in 3.4.0, highly recommended to leverage it to help with this.

@LETMECALM
Copy link
Author

How to use Memory Tracker ?

@wey-gu
Copy link
Contributor

wey-gu commented Oct 30, 2023

Why isn't the memory space being released?

It's about storaged, not graphd, right?
There are caches(rocksDB) there, which are configurable, too(see storaged configuration docs, and rocksdb docs).

@QingZ11 QingZ11 added the type/question Type: question about the product label Oct 30, 2023
@QingZ11
Copy link
Contributor

QingZ11 commented Feb 18, 2024

Hi, I have noticed that the issue you created hasn’t been updated for nearly a month, so I have to close it for now. If you have any new updates, you are welcome to reopen this issue anytime.

Thanks a lot for your contribution anyway 😊

@QingZ11 QingZ11 closed this as completed Feb 18, 2024
@peak-xu
Copy link

peak-xu commented Sep 20, 2024

OOM

"Memory Tracker" was introduced in 3.4.0, highly recommended to leverage it to help with this.

Must it be a container environment to use memory tracker?

@wey-gu
Copy link
Contributor

wey-gu commented Sep 20, 2024

OOM

"Memory Tracker" was introduced in 3.4.0, highly recommended to leverage it to help with this.

Must it be a container environment to use memory tracker?

no , it's supported on both container and bare metal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/question Type: question about the product
Projects
None yet
Development

No branches or pull requests

5 participants