Finally I should add , going back to 0.92.1 got cluster back on feet. It does not prove anything though, I might've got lucky!
On Fri, Aug 24, 2012 at 1:58 PM, Shrijeet Paliwal <shrij...@rocketfuel.com>wrote: > Sorry sent too early by mistake. > Continuing.. > > I upgraded three data centers to our own checkout of 0.92.2. Two went > fine, upgrade to one data center failed. Failed in the sense that > ROOT and META assignment took unusually long. Panic struck I restarted > master and all region servers and managed to get ROOT assigned. > But META assignment got stuck badly. > > The log is here : > https://raw.github.com/gist/3455435/adebd118b47aa3d715201010aa09e5eb8930033c/npe_rs_0.92.2.log > > Notice how region server was stuck in a loop of NPE (grep > processBatchCallback). > There is one more NPE related to zookeeper constructor. > > JD was there at irc channel and he thought it could be regression. > > On Fri, Aug 24, 2012 at 1:52 PM, Shrijeet Paliwal <shrij...@rocketfuel.com > > wrote: > >> Hi, >> >> I wanted to report one more issue. Recently I upgraded three data centers >> to our own checkout of 0.92.2, last commit : >> >> commit 5accb6a1be4776630126ac21d07adb652b74df95 >> Author: Zhihong Yu <te...@apache.org> >> Date: Mon Aug 20 18:19:45 2012 +0000 >> 24 >> HBASE-6608 Fix for HBASE-6160, META entries from daughters can be deleted >> before parent entries, shouldn't compare HRegionInfo's (Enis) >> >> >> >> On Fri, Aug 24, 2012 at 12:55 PM, Dave Wang <d...@cloudera.com> wrote: >> >>> I believe this would be solved by a backport of HBASE-6211 into 0.92.x. >>> >>> - Dave >>> >>> On Fri, Aug 24, 2012 at 12:28 PM, Stack <st...@duboce.net> wrote: >>> >>> > On Fri, Aug 24, 2012 at 11:57 AM, Shrijeet Paliwal >>> > <shrij...@rocketfuel.com> wrote: >>> > > 0.92.2 has following error messages in region server logs (while it >>> is >>> > > initializing RegionServerMetrics). Some one reported it here >>> > > https://issues.apache.org/jira/browse/HBASE-6514 . >>> > > >>> > > 1591 2012-08-22 20:08:28,106 ERROR >>> > org.apache.hadoop.metrics.MetricsUtil: >>> > > unknown metrics type: >>> > > org.apache.hadoop.hbase.metrics.histogram.MetricsHistogram >>> > > 1592 2012-08-22 20:08:28,106 ERROR >>> > org.apache.hadoop.metrics.MetricsUtil: >>> > > unknown metrics type: >>> > > org.apache.hadoop.hbase.metrics.histogram.MetricsHistogram >>> > > 1593 2012-08-22 20:08:28,106 ERROR >>> > org.apache.hadoop.metrics.MetricsUtil: >>> > > unknown metrics type: >>> > > org.apache.hadoop.hbase.metrics.histogram.MetricsHistogram >>> > > 1594 2012-08-22 20:08:28,106 ERROR >>> > org.apache.hadoop.metrics.MetricsUtil: >>> > > unknown metrics type: >>> org.apache.hadoop.hbase.metrics.ExactCounterMetric >>> > > 1595 2012-08-22 20:08:28,106 ERROR >>> > org.apache.hadoop.metrics.MetricsUtil: >>> > > unknown metrics type: >>> > > org.apache.hadoop.hbase.metrics.histogram.MetricsHistogram >>> > > 1596 2012-08-22 20:08:28,107 ERROR >>> > org.apache.hadoop.metrics.MetricsUtil: >>> > > unknown metrics type: >>> > > org.apache.hadoop.hbase.metrics.histogram.MetricsHistogram >>> > > >>> > > Is this known? >>> > > >>> > >>> > I pulled it in as a blocker on 0.92.2. Will take a looksee. Thanks >>> > Shrijeet. >>> > St.Ack >>> > >>> >> >> >
