Hi All,
Sean patiently worked with me in solving this issue. The problem was
entirely my fault in settings MAVEN_OPTS env variable was set and was
overriding everything.
--Ben
On Tue, Sep 8, 2015 at 1:37 PM, Benjamin Zaitlen wrote:
> Yes, just reran with the following
>
>
Hi All,
I'm trying to build a distribution off of the latest in master and I keep
getting errors on MQTT and the build fails. I'm running the build on a
m1.large which has 7.5 GB of RAM and no other major processes are running.
MAVEN_OPTS="-Xmx2g -XX:MaxPermSize=512M
Ah, right. Should've caught that.
The docs seem to recommend 2gb. Should that be increased as well?
--Ben
On Tue, Sep 8, 2015 at 9:33 AM, Sean Owen wrote:
> It shows you there that Maven is out of memory. Give it more heap. I use
> 3gb.
>
> On Tue, Sep 8, 2015 at 1:53
It shows you there that Maven is out of memory. Give it more heap. I use 3gb.
On Tue, Sep 8, 2015 at 1:53 PM, Benjamin Zaitlen wrote:
> Hi All,
>
> I'm trying to build a distribution off of the latest in master and I keep
> getting errors on MQTT and the build fails. I'm
I'm still getting errors with 3g. I've increase to 4g and I'll report back
To be clear:
export MAVEN_OPTS="-Xmx4g -XX:MaxPermSize=1024M
-XX:ReservedCodeCacheSize=1024m"
[ERROR] GC overhead limit exceeded -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven
Do you run Zinc while compiling ?
Cheers
On Tue, Sep 8, 2015 at 7:56 AM, Benjamin Zaitlen wrote:
> I'm still getting errors with 3g. I've increase to 4g and I'll report back
>
> To be clear:
>
> export MAVEN_OPTS="-Xmx4g -XX:MaxPermSize=1024M
>
It might need more memory in certain situations / running certain
tests. If 3gb works for your relatively full build, yes you can open a
PR to change any occurrences of lower recommendations to 3gb.
On Tue, Sep 8, 2015 at 3:02 PM, Benjamin Zaitlen wrote:
> Ah, right.
Yes, just reran with the following
(spark_build)root@ip-10-45-130-206:~/spark# export MAVEN_OPTS="-Xmx4096mb
> -XX:MaxPermSize=1024M -XX:ReservedCodeCacheSize=1024m"
> (spark_build)root@ip-10-45-130-206:~/spark# build/mvn -Pyarn -Phadoop-2.4
> -Dhadoop.version=2.4.0 -DskipTests clean package
I'm running zinv while compiling. It seems that MAVEN_OPTS doesn't really
change much? Or perhaps I'm misunderstanding something -- grepping for
java i see
root 24355 102 8.8 4687376 1350724 pts/4 Sl 16:51 11:08
> /usr/lib/jvm/java-7-openjdk-amd64/bin/java -server -Xmx2g
>
MAVEN_OPTS shouldn't affect zinc as it's an unrelated application. You
can run "zinc -J-Xmx4g..." in general, but in the provided script,
ZINC_OPTS seems to be the equivalent, yes. It kind of looks like your
mvn process isn't getting any special memory args there. Is MAVEN_OPTS
really exported?
10 matches
Mail list logo