I didn't think about it like that. I just figured that HBase would block certain components until the cluster is stable. However, like you said, since I configured my Observer as a system coprocessor, your explanation makes sense. I'll have to come up with another example. Thank you for your answer and the great explanation.
On Fri, May 25, 2012 at 2:31 PM, Andrew Purtell <[email protected]> wrote: > > When I restart my HBase cluster the cluster does not ever finish > assigning > > META region. In the master's log there are a lot of > > NotServingRegionExceptions: Region is not online: .META.,,1. Other than > > that I can't see any log messages that indicate any specific about > loading > > the coprocessor. If I then comment out the coprocessor property in > > hbase-site.xml and restart the cluster, then HBase starts up fine. > > In the future, check the regionserver logs. Why is META not able to deploy? > > In this case, you should know that Observers installed as system > coprocessors, i.e. by way of site file properties like > hbase.coprocessor.region.classes, are also installed on the META > region. Your code is trying to find a user table via getTable before > META is deployed. That can't work. The exception generated fails the > open of the META region. > > Best regards, > > - Andy > > Problems worthy of attack prove their worth by hitting back. - Piet > Hein (via Tom White) >
