[
https://issues.apache.org/jira/browse/PHOENIX-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13929897#comment-13929897
]
Hudson commented on PHOENIX-131:
--------------------------------
SUCCESS: Integrated in Apache Phoenix - Branch:master #130 (See
[https://builds.apache.org/job/Phoenix/130/])
PHOENIX-131 Incorrect determination of total available memory (JamesTaylor)
(jamestaylor: rev cb7763d3dfe2eb42f9dbc3e6147859932c13e0f1)
* phoenix-core/src/main/java/org/apache/phoenix/query/BaseQueryServicesImpl.java
* phoenix-core/src/main/java/org/apache/phoenix/cache/GlobalCache.java
> Incorrect determination of total available memory
> -------------------------------------------------
>
> Key: PHOENIX-131
> URL: https://issues.apache.org/jira/browse/PHOENIX-131
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Priority: Critical
> Fix For: 3.0.0, 4.0.0
>
> Attachments: totalMem.patch
>
>
> Instead of using Runtime.getRuntime().maxMemory() to get the total memory, we
> were using Runtime.getRuntime().totalMemory(). Fixing this and we'll have *a
> lot* more memory available for GROUP BY and joins.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
