[
https://issues.apache.org/jira/browse/TAJO-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14164750#comment-14164750
]
Hudson commented on TAJO-1110:
------------------------------
SUCCESS: Integrated in Tajo-master-CODEGEN-build #49 (See
[https://builds.apache.org/job/Tajo-master-CODEGEN-build/49/])
TAJO-1110: JAVA_PULLSERVER_HEAP_MAX in bin/tajo should be increased. (hyunsik:
rev 27079643b5b62fc1f6196f3b6c2a794256097663)
* tajo-dist/src/main/bin/tajo
* CHANGES
> JAVA_PULLSERVER_HEAP_MAX in bin/tajo should be increased
> --------------------------------------------------------
>
> Key: TAJO-1110
> URL: https://issues.apache.org/jira/browse/TAJO-1110
> Project: Tajo
> Issue Type: Bug
> Components: conf and scripts
> Affects Versions: 0.9.0
> Reporter: Hyunsik Choi
> Assignee: Hyunsik Choi
> Priority: Trivial
> Fix For: 0.9.0
>
>
> We can separate TajoPullServer to another Java processor in order to mitigate
> the performance degradation caused by GC. TajoPullServer uses
> {{JAVA_PULLSERVER_HEAP_MAX}} to specify the max heap of TajoPullServer java
> processor. Currently, it is set to 100MB. It is somewhat smaller than usual
> size clusters. This patch changes the HEAP_MAP to 1000MB which seems to be
> proper in usual size clusters.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
