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

Alex Rodoni closed IMPALA-7050.
-------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 3.1.0
                   Impala 2.13.0

> Impala Doc: Document inc_stats_size_limit_bytes command line option for 
> Impalad
> -------------------------------------------------------------------------------
>
>                 Key: IMPALA-7050
>                 URL: https://issues.apache.org/jira/browse/IMPALA-7050
>             Project: IMPALA
>          Issue Type: Task
>          Components: Docs
>    Affects Versions: Impala 2.8.0
>            Reporter: Alex Rodoni
>            Assignee: Alex Rodoni
>            Priority: Major
>             Fix For: Impala 2.13.0, Impala 3.1.0
>
>
> nformation -
> ======
> -inc_stats_size_limit_bytes (Maximum size of incremental stats the catalog
> is allowed to serialize per table. This limit is set as a safety check,
> to prevent the JVM from hitting a maximum array limit of 1GB (or OOM)
> while building the thrift objects to send to impalads. By default, it's
> set to 200MB) type: int64 default: 209715200
> ======
> Way to modify:
> ============
> You can change inc_stats_size_limit_bytes value using the below steps:
> 1. CM > Impala Service > Configuration > Search Impala Command Line Argument 
> Advanced Configuration Snippet (Safety Valve)
> 2. Please input -inc_stats_size_limit_bytes=<value> 
> Please note that: you have to input the integer value in <value> 
> For example, if you want to set 1GB, please input 1048576000(1024*1024*1024).
> 3. Please save it and restart the impala service



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org

Reply via email to