[
https://issues.apache.org/jira/browse/GRIFFIN-295?focusedWorklogId=337290&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-337290
]
ASF GitHub Bot logged work on GRIFFIN-295:
------------------------------------------
Author: ASF GitHub Bot
Created on: 01/Nov/19 12:10
Start Date: 01/Nov/19 12:10
Worklog Time Spent: 10m
Work Description: wankunde commented on issue #546: [GRIFFIN-295]Limit
the memory used by test case
URL: https://github.com/apache/griffin/pull/546#issuecomment-548766442
Hi, @joohnnie
First, as I described in this PR, the maven memory can be limited used by
setting MAVEN_OPTS, which is required. But we also need to limit the spark jobs
memory because JVM stores many unused objects before full GC occurs. SPARK
project also sets this configuration .
https://github.com/apache/spark/blob/14337f68e328c3faad81d3051a56be080a31509d/pom.xml#L2329
https://github.com/apache/spark/blob/14337f68e328c3faad81d3051a56be080a31509d/pom.xml#L2379
Second, there was a `No output has been received in the last 10m0s` error,
and I don't know what's wrong with the travis build container, so printing more
log message helps troubleshoot.
https://travis-ci.org/apache/griffin/builds/605545271?utm_medium=notification&utm_source=github_status
```
No output has been received in the last 10m0s, this potentially indicates a
stalled build or something wrong with the build itself.
Check the details on how to adjust your build configuration on:
https://docs.travis-ci.com/user/common-build-problems/#build-times-out-because-no-output-was-received
The build has been terminated
```
What do you think, @joohnnie
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 337290)
Time Spent: 1h 20m (was: 1h 10m)
> Limit the memory used by test case
> ----------------------------------
>
> Key: GRIFFIN-295
> URL: https://issues.apache.org/jira/browse/GRIFFIN-295
> Project: Griffin
> Issue Type: Improvement
> Reporter: Wan Kun
> Priority: Major
> Attachments: 1.png, 2.png, 3.png, 4.png
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> The container memory size is 3G in travis, but out test cases always uses
> more than 3G memory, so `Cannot allocate memory` will be thrown.
>
> {code:java}
> Java HotSpot(TM) 64-Bit Server VM warning: INFO:
> os::commit_memory(0x00000000fe980000, 23592960, 0) failed; error='Cannot
> allocate memory' (errno=12)
> #
> # There is insufficient memory for the Java Runtime Environment to continue.
> # Native memory allocation (mmap) failed to map 23592960 bytes for committing
> reserved memory.
> # An error report file with more information is saved as:
> # /home/travis/build/apache/griffin/measure/hs_err_pid11948.log
> # [ timer expired, abort... ]
> {code}
>
> There are two kind of programs in our tests, the maven main program and the
> tests run by maven-surefire-plugin and scalatest-maven-plugin.
> If the memory is not limited, test cases will occupy as much memory as
> possible especially spark jobs.
> Spark jobs will not free the memory until a full GC occurs , even if we have
> stopped the spark context .so we need to limit the momery used by test cases.
> We can limit the maven memory used by set export MAVEN_OPTS=" -Xmx1024m
> -XX:ReservedCodeCacheSize=128m" , and we can limit the memory used by spark
> job tests by configuring the maven-surefire-plugin and scalatest-maven-plugin.
>
> For example:
> Before we limit the memory used, maven program occupy 1.5G memory and spark
> job occupy 1.8G memory.
> !1.png!
> !2.png!
>
> After we limit the memory used, maven program occupy 1G memory and spark job
> occupy 1G memory.
>
> !3.png!
>
> !4.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
