Jiajun,
Your problem isn't coprocessor related, per those logs. It appears
that one of the regions Master tried to look up in your .META. entries
had no region info associated with it (and hence got a null). Before
upgrading, did your hbck report proper health? Does your master not
start at all due to this?
On Mon, Mar 12, 2012 at 7:54 PM, Jiajun Chen <cjjvict...@gmail.com> wrote:
> 2012-03-12 22:05:50,736 DEBUG
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation:
> Cached location for .META.,,1.1028785192 is slave184.uc.uuwatch.com:60020
> 2012-03-12 22:05:50,736 DEBUG
> org.apache.hadoop.hbase.client.HTable$ClientScanner: Creating scanner over
> .META. starting at key ''
> 2012-03-12 22:05:50,736 DEBUG
> org.apache.hadoop.hbase.client.HTable$ClientScanner: Advancing internal
> scanner to startKey at ''
> 2012-03-12 22:05:52,291 DEBUG
> org.apache.hadoop.hbase.client.HTable$ClientScanner: Finished with scanning
> at {NAME => '.META.,,1', STARTKEY => '', ENDKEY => '', ENCODED =>
> 1028785192,}
> 2012-03-12 22:05:52,821 FATAL org.apache.hadoop.hbase.master.HMaster:
> Master server abort: loaded coprocessors are: []
> 2012-03-12 22:05:52,822 FATAL org.apache.hadoop.hbase.master.HMaster:
> Unhandled exception. Starting shutdown.
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.master.AssignmentManager.rebuildUserRegions(AssignmentManager.java:2190)
> at
> org.apache.hadoop.hbase.master.AssignmentManager.joinCluster(AssignmentManager.java:323)
> at
> org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:501)
> at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:326)
> at java.lang.Thread.run(Thread.java:662)
> 2012-03-12 22:05:52,832 INFO org.apache.hadoop.hbase.master.HMaster:
> Aborting
> 2012-03-12 22:05:52,833 DEBUG org.apache.hadoop.hbase.master.HMaster:
> Stopping service threads
> 2012-03-12 22:05:52,833 INFO org.apache.hadoop.ipc.HBaseServer: Stopping
> server on 60000
> 2012-03-12 22:05:52,833 INFO org.apache.hadoop.ipc.HBaseServer: IPC Server
> handler 0 on 60000: exiting
>
> In the Apache HBase Reference Guide :
> hbase.coprocessor.master.classes
>
> A comma-separated list of
> org.apache.hadoop.hbase.coprocessor.MasterObserver coprocessors that are
> loaded by default on the active HMaster process. For any implemented
> coprocessor methods, the listed classes will be called in order. After
> implementing your own MasterObserver, just put it in HBase's classpath and
> add the fully qualified class name here.
>
> Default:
>
> which class should I use ?
--
Harsh J
