[
https://issues.apache.org/jira/browse/IMPALA-5118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong resolved IMPALA-5118.
-----------------------------------
Resolution: Won't Fix
We removed the unlimited option in IMPALA-5653 so this isn't really relevant
any more.
> CmImpalad.find_process_mem_mb_limit() returns -1 if mem_limit is set to -1 in
> the CM to indicate unlimited
> ----------------------------------------------------------------------------------------------------------
>
> Key: IMPALA-5118
> URL: https://issues.apache.org/jira/browse/IMPALA-5118
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
> Affects Versions: Impala 2.9.0
> Reporter: Matthew Mulder
> Priority: Minor
>
> In the Cloudera Manager configuration page for Impalad, the mem_limit field
> can be set to "-1" to indicate unlimited memory. In the test infrastructure,
> CmImpalad.find_process_mem_mb_limit() apparently queries the CM for this
> value and interprets a "-1" literally. This results in the stress test
> getting an error when it tries{code}SET MEM_LIMIT=-1M{code}I'm not sure if
> CmImpalad.find_process_mem_mb_limit() should return sys.maxint in this case
> because I'm not sure what affect that would have on the stress test.
> The workaround is to set mem_limit to some positive value and restart the
> impalads.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
