You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Xiong LIU (JIRA)" <ji...@apache.org> on 2013/06/22 04:56:22 UTC

[jira] [Created] (HBASE-8790) NullPointerException throwed when stopping regionserver

Xiong LIU created HBASE-8790:
--------------------------------

             Summary: NullPointerException throwed when stopping regionserver
                 Key: HBASE-8790
                 URL: https://issues.apache.org/jira/browse/HBASE-8790
             Project: HBase
          Issue Type: Bug
          Components: regionserver
    Affects Versions: 0.95.1
         Environment: CentOS 5.9 x86_64, java version "1.6.0_45"
            Reporter: Xiong LIU


The Hbase cluster is a fresh start with one regionserver.
When we stop hbase, an unhandled NullPointerException is throwed in the regionserver.
The regionserver's log is as follows:

2013-06-21 10:21:11,284 INFO  [regionserver61020] regionserver.HRegionServer: Closing user regions
2013-06-21 10:21:14,288 DEBUG [regionserver61020] regionserver.HRegionServer: Waiting on 1028785192
2013-06-21 10:21:14,290 FATAL [regionserver61020] regionserver.HRegionServer: ABORTING region server HOSTNAME_TEST,61020,1371781086817
: Unhandled: null
java.lang.NullPointerException
        at org.apache.hadoop.hbase.regionserver.HRegionServer.tryRegionServerReport(HRegionServer.java:988)
        at org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:832)
        at java.lang.Thread.run(Thread.java:662)
2013-06-21 10:21:14,292 FATAL [regionserver61020] regionserver.HRegionServer: RegionServer abort: loaded coprocessors are: [org.apache
.hadoop.hbase.coprocessor.MultiRowMutationEndpoint]
2013-06-21 10:21:14,293 INFO  [regionserver61020] regionserver.HRegionServer: STOPPED: Unhandled: null
2013-06-21 10:21:14,293 INFO  [regionserver61020] ipc.RpcServer: Stopping server on 61020

It seems that after closing user regions, the rssStub is null.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira