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

Tim Armstrong resolved IMPALA-5653.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 2.11.0


  IMPALA-5653: Remove "unlimited" process mem_limit option

This was deprecated in 2.10. Now we can disable it.

Testing:
Started a minicluster with --mem_limit="" and --mem_limit=-1,
confirmed that it didn't start up and logged a reasonable
error in both cases.

  E0825 09:23:59.749104 32708 impalad-main.cc:95] Impalad services did
    not start correctly, exiting.  Error: The process memory limit
    (--mem_limit) must be a positive bytes value or percentage: -1

Change-Id: Ifb235ae34ce8d2aff37f0fa0c218419da01b30f3
Reviewed-on: http://gerrit.cloudera.org:8080/7828
Reviewed-by: Dan Hecht <dhe...@cloudera.com>
Tested-by: Impala Public Jenkins

> Remove "unlimited" process mem_limit option
> -------------------------------------------
>
>                 Key: IMPALA-5653
>                 URL: https://issues.apache.org/jira/browse/IMPALA-5653
>             Project: IMPALA
>          Issue Type: Task
>          Components: Backend
>            Reporter: Tim Armstrong
>            Assignee: Tim Armstrong
>            Priority: Minor
>              Labels: resource-management
>             Fix For: Impala 2.11.0
>
>
> The ability to set an "unlimited" process mem limit is unnecessary (since you 
> can configure the process limit to be arbitrarily large) and causes some 
> complications in the code. It is also not tested automatically. We should 
> remove this support in 2.11 after we officially deprecate it in 2.10 
> (IMPALA-5652).



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

Reply via email to