geekboood commented on issue #10960: URL: https://github.com/apache/pinot/issues/10960#issuecomment-1632644587
> When configuring xmx16G, java will use up to 16G heap and up to 16G direct memory, mapped memory is not tracked though. The mapped memory can go over the limit (OS should reclaim mapped memory when it is short on memory, but that might be too late). One best practice is to not put limit for the memory assuming pinot server is the only pod running on the node I think this is the reason. Cgroup won't calculate mmap committed memory seperately, so the oom killer will kick in before kernel reclaim these memory. However, I found another mysterious problem. When I run a same query repeatly (I only have offline table so the data should be consistent), RES memory keeps increasing. I think this might not be right... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org For additional commands, e-mail: commits-h...@pinot.apache.org
