[
https://issues.apache.org/jira/browse/IMPALA-7941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16754693#comment-16754693
]
Tim Armstrong commented on IMPALA-7941:
---------------------------------------
[~arodoni_cloudera] I think
https://impala.apache.org/docs/build/html/topics/impala_mem_limit.html needs to
be updated because it references the old algorithm. I think it's minor so will
just write up the change while I'm looking at it - I created a subtask.
> Determine process memory limit from cgroups limit, if set
> ---------------------------------------------------------
>
> Key: IMPALA-7941
> URL: https://issues.apache.org/jira/browse/IMPALA-7941
> Project: IMPALA
> Issue Type: New Feature
> Components: Backend
> Reporter: Tim Armstrong
> Assignee: Tim Armstrong
> Priority: Major
> Labels: admission-control, resource-management
> Fix For: Impala 3.2.0
>
> Attachments: allocmem.cc
>
>
> We currently take the hardcoded config value, or the system physical memory
> if that is not set. We could be smarter when running in a container by
> sniffing out the cgroups setting.
> Java did something along this lines:
> https://www.opsian.com/blog/java-on-docker/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
