[
https://issues.apache.org/jira/browse/KUDU-3241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Serbin resolved KUDU-3241.
---------------------------------
Fix Version/s: n/a
Resolution: Information Provided
Hi,
We use this JIRA to track detailed bug reports (ideally, with root cause
analysis already performed) and detailed requests for improvements and features.
I think your question can be handled better if using the Slack channel or user
mailing list: you could get more feedback and faster answers there, and it's
more interactive than JIRA. Please raise your question at #getkudu Slack
channel (https://getkudu-slack.herokuapp.com/) or post a message to Kudu user
mailing list: https://kudu.apache.org/community.html
>From what I can see, that set of symptoms might be a manifestation of
>KUDU-2836: it's fixed in Kudu 1.11 release.
Thank you!
Kind regards,
Alexey
> System under memory pressure (414.25% of limit used). However, there are no
> ops currently runnable which would free memory
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: KUDU-3241
> URL: https://issues.apache.org/jira/browse/KUDU-3241
> Project: Kudu
> Issue Type: Task
> Components: tserver
> Affects Versions: 1.10.0
> Environment: centos 7.7
> Reporter: sun
> Priority: Major
> Fix For: n/a
>
>
> hi everybody，
> When I use kudu to store data in the production environment, I find that the
> memory of kudu tserver is not limited, or is constantly consuming the memory
> of the operating system, and I have not found an effective patch to fix this
> problem。
> One of my tserver, totally 256G memory, gflags:
> -memory_limit_hard_bytes= 26843545600 (25G) -memory_limit_soft_percentage=85
> -memory_pressure_percentage=80
> but in "top" and webui of tserver ,i find memory is used over 25G ,and then
> kill tserver because of OOM.
> could anybody give me some tips? thanks in advance.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
