hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Marc Spaggiari <jean-m...@spaggiari.org>
Subject Re: [VOTE] Sixth release candidate for HBase 1.0.0 (RC5) is available. Please vote by Feb 19 2015
Date Wed, 18 Feb 2015 20:17:48 GMT
Comments inlined too ;)




> > Download and un-packed passed.
> >
> > Checked Changes.txt => Passed.
> > Checked documentation => Link "Why does HBase care about /etc/hosts?
> > <http://devving.com/?p=414>" in section "Quick Start - Standalone HBase"
> > doesn't work
> >
>
> Seems like a minor issue.
>

Even smaller than that ;)


>
> > Run test suite => Failed 3 time in a row with JDK 1.7
> > Failed tests:
> >   TestNodeHealthCheckChore.testHealthCheckerFail:69->healthCheckerTest:90
> > expected:<FAILED> but was:<FAILED_WITH_EXCEPTION>
> >
> >
> TestNodeHealthCheckChore.testHealthCheckerSuccess:63->healthCheckerTest:90
> > expected:<SUCCESS> but was:<FAILED_WITH_EXCEPTION>
> >
> >
> TestNodeHealthCheckChore.testHealthCheckerTimeout:75->healthCheckerTest:90
> > expected:<TIMED_OUT> but was:<FAILED_WITH_EXCEPTION>
> >
>
> These tests run a shell script. It maybe something env related.
>

Got it. I wil take another look and see why. Passed with JDK1.8 this
time... Will try multiple times and report if any issue.


>
>
> >
> > Tests in error:
> >
> >
> org.apache.hadoop.hbase.http.TestSSLHttpServer.org.apache.hadoop.hbase.http.TestSSLHttpServer
> >   Run 1: TestSSLHttpServer.setup:71 ยป Certificate Subject class type
> > invalid.
> >   Run 2: TestSSLHttpServer.cleanup:102 NullPointer
> >
>
> JDK-8 is supported, but not tested extensively. We can fix this if we can
> find the root cause, but not a reason to block the release.
>

Fine for me. I will try to find the related exceptions from the logs...

 java.security.cert.CertificateException: Subject class type invalid.
        at sun.security.x509.X509CertInfo.setSubject(X509CertInfo.java:888)
        at sun.security.x509.X509CertInfo.set(X509CertInfo.java:415)
        at
org.apache.hadoop.hbase.http.ssl.KeyStoreTestUtil.generateCertificate(KeyStoreTestUtil.java:94)
        at
org.apache.hadoop.hbase.http.ssl.KeyStoreTestUtil.setupSSLConfig(KeyStoreTestUtil.java:246)
        at
org.apache.hadoop.hbase.http.TestSSLHttpServer.setup(TestSSLHttpServer.java:71)

Wich points to  info.set(X509CertInfo.SUBJECT, new
CertificateSubjectName(owner));
Where  owner = new X500Name(dn);

I think it's related to https://issues.apache.org/jira/browse/HBASE-12006


> >
> > While running in standalone got this exception in the logs when clicking
> on
> > Debug Dump in the master interface:
> > 2015-02-16 10:19:39,172 ERROR [666059465@qtp-2106900153-3] mortbay.log:
> > /dump
> > java.lang.NullPointerException
> >     at
> >
> >
> org.apache.hadoop.hbase.regionserver.RSDumpServlet.dumpQueue(RSDumpServlet.java:106)
> >     at
> >
> >
> org.apache.hadoop.hbase.master.MasterDumpServlet.doGet(MasterDumpServlet.java:105)
> >     at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
> >     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
> >     at
> > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
> >     at
> >
> >
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1221)
> >     at
> >
> >
> org.apache.hadoop.hbase.http.lib.StaticUserWebFilter$StaticUserFilter.doFilter(StaticUserWebFilter.java:113)
> >     at
> >
> >
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> >     at
> >
> >
> org.apache.hadoop.hbase.http.HttpServer$QuotingInputFilter.doFilter(HttpServer.java:1351)
> >     at
> >
> >
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> >     at
> >
> org.apache.hadoop.hbase.http.NoCacheFilter.doFilter(NoCacheFilter.java:49)
> >     at
> >
> >
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> >     at
> >
> org.apache.hadoop.hbase.http.NoCacheFilter.doFilter(NoCacheFilter.java:49)
> >     at
> >
> >
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> >     at
> > org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399)
> >     at
> >
> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
> >     at
> > org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
> >     at
> > org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
> >     at
> > org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
> >     at
> >
> >
> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
> >     at
> > org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
> >     at org.mortbay.jetty.Server.handle(Server.java:326)
> >     at
> > org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
> >     at
> >
> >
> org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)
> >     at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
> >     at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
> >     at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
> >     at
> >
> >
> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
> >     at
> >
> >
> org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
> >
>
> This maybe because the master was not fully up? Did the exception go away?
>

Master is fully running. I'm able to create tables from the shell, but
still getting this exception.


JM

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