hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sheena O'Connell" <sheena.oconn...@gmail.com>
Subject Re: Switching to Java 7
Date Mon, 08 Dec 2014 16:16:18 GMT
Re g cloud,  as far as I can tell what they want is a writeup for existing
services. So we get healthstat running and then write up what we can do in
terms of data flow managment and visualisation then that should cut it.

It would be nice to put the calculator on there as software as a service,
but it needs much more polish
On 8 Dec 2014 02:59, "Ted Yu" <yuzhihong@gmail.com> wrote:

> Looking at the test failures of
> https://builds.apache.org/job/Hadoop-Hdfs-trunk/1963/ which uses jdk 1.7:
>
> e.g.
>
> https://builds.apache.org/job/Hadoop-Hdfs-trunk/1963/testReport/junit/org.apache.hadoop.hdfs.server.namenode.snapshot/TestRenameWithSnapshots/testRenameFileAndDeleteSnapshot/
>
> java.lang.OutOfMemoryError: Java heap space
>         at sun.nio.ch.EPollArrayWrapper.<init>(EPollArrayWrapper.java:120)
>         at sun.nio.ch.EPollSelectorImpl.<init>(EPollSelectorImpl.java:68)
>         at
> sun.nio.ch.EPollSelectorProvider.openSelector(EPollSelectorProvider.java:36)
>         at
> io.netty.channel.nio.NioEventLoop.openSelector(NioEventLoop.java:126)
>         at io.netty.channel.nio.NioEventLoop.<init>(NioEventLoop.java:120)
>         at
> io.netty.channel.nio.NioEventLoopGroup.newChild(NioEventLoopGroup.java:87)
>         at
> io.netty.util.concurrent.MultithreadEventExecutorGroup.<init>(MultithreadEventExecutorGroup.java:64)
>
>
> Should more heap be given to the tests ?
>
>
> Cheers
>
>
> On Sun, Dec 7, 2014 at 2:09 PM, Steve Loughran <stevel@hortonworks.com>
> wrote:
>
> > The latest migration status:
> >
> >   if the jenkins builds are happy then the patch will go in -I do that
> > monday morning 10:00 UTC
> >
> > https://builds.apache.org/view/H-L/view/Hadoop/
> >
> > Getting jenkins to work has been "surprisingly difficult"...it turns out
> > that those builds which we thought were java7 or java8 weren't, as
> setting
> >   export JAVA_HOME=${TOOLS_HOME}/java/latest
> >
> > meant that they picked up a java 6 machine
> >
> > Now the trunk precommit/postcommit and scheduled branches should have
> > export JAVA_HOME=${TOOLS_HOME}/java/jdk1.7.0_55
> >
> > the Java 8 builds have more changes
> >
> > export JAVA_HOME=${TOOLS_HOME}/java/jdk1.8.0
> > export MAVEN_OPTS="-Xmx3072m -XX:MaxPermSize=768m"
> > and  -Dmaven.javadoc.skip=true  on the mvn builds
> >
> > without these javadocs fails and test runs OOM.
> >
> > We need to have something resembling the nightly build env setup again,
> > git/Svn stored file with something for java8 alongside the normal env
> vars.
> >
> > --
> > CONFIDENTIALITY NOTICE
> > NOTICE: This message is intended for the use of the individual or entity
> to
> > which it is addressed and may contain information that is confidential,
> > privileged and exempt from disclosure under applicable law. If the reader
> > of this message is not the intended recipient, you are hereby notified
> that
> > any printing, copying, dissemination, distribution, disclosure or
> > forwarding of this communication is strictly prohibited. If you have
> > received this communication in error, please contact the sender
> immediately
> > and delete it from your system. Thank You.
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message