[ 
https://issues.apache.org/jira/browse/IMPALA-5661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tim Armstrong resolved IMPALA-5661.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 2.10.0



IMPALA-5661: buffer pool limit

Adds the --buffer_pool_limit flag to control the buffer pool size.
It can be specified as either an absolute memory value or a percentage
of the process memory limit

Testing:
Started up a cluster with --buffer_pool_limit=10%, confirmed via
/metrics page that the buffer pool limit was reduced to ~800MB on
my system.

Change-Id: Ia64e21e0d5a7cf35a9064f365c6c86db13fbd73d
Reviewed-on: http://gerrit.cloudera.org:8080/7462
Reviewed-by: Matthew Jacobs <m...@cloudera.com>
Tested-by: Impala Public Jenkins

> Consider allowing configuration of buffer pool size
> ---------------------------------------------------
>
>                 Key: IMPALA-5661
>                 URL: https://issues.apache.org/jira/browse/IMPALA-5661
>             Project: IMPALA
>          Issue Type: Sub-task
>          Components: Backend
>    Affects Versions: Impala 2.10.0
>            Reporter: Tim Armstrong
>            Assignee: Tim Armstrong
>              Labels: resource-management
>             Fix For: Impala 2.10.0
>
>
> Currently the buffer pool size is hard-coded to be 80% of the process memory 
> limit. We expect that this is a reasonable default but it may be useful to 
> add a safety value command line argument to allow control over this.
> E.g. 
> --buffer_pool_limit=80% would be the default, and it could be set to values 
> like --buffer_pool_size=70% or --buffer_pool_size=40g



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to