You can use hbck to fix it: hbase hbck -fixMeta -fixAssignments
If that doesn't work, can you restart the region server that holds the ROOT region? Thanks, Jimmy On Fri, Sep 6, 2013 at 3:56 AM, enes yücer <[email protected]> wrote: > Hi, > > I'm using cdh 4.2.0 and hbase 0.94.2. our cluster working on 12 nodes. > > when I scan table in hbase shell or java api, it return: > > ERROR: org.apache.hadoop.hbase.client.NoServerForRegionException: Unable to > find region for <table_name>,,99999999999999 after 7 tries. > > I am getting same exception when runnig "sudo -u hbase hbase hbck -repair". > > One region looks unassigned in web ui and hbase zkcli. > > my hbase master log: > > 1:54:07.226 PMINFOorg.apache.hadoop.hbase.master.AssignmentManager > > Region has been CLOSING for too long, this should eventually complete > or the server will expire, send RPC again > > 1:54:17.227 PMINFOorg.apache.hadoop.hbase.master.AssignmentManager > > Regions in transition timed out: -ROOT-,,0.70236052 state=CLOSING, > ts=1378296338838, server=bda1node01.etiya.com,60000,1378296027149 > > 1:54:17.227 PMINFOorg.apache.hadoop.hbase.master.AssignmentManager > > Region has been CLOSING for too long, this should eventually complete > or the server will expire, send RPC again > > 1:54:27.226 PMINFOorg.apache.hadoop.hbase.master.AssignmentManager > > Regions in transition timed out: -ROOT-,,0.70236052 state=CLOSING, > ts=1378296338838, server=bda1node01.etiya.com,60000,1378296027149 > > 1:54:27.226 PMINFOorg.apache.hadoop.hbase.master.AssignmentManager > > Region has been CLOSING for too long, this should eventually complete > or the server will expire, send RPC again > > 1:54:37.226 PMINFOorg.apache.hadoop.hbase.master.AssignmentManager > > Regions in transition timed out: -ROOT-,,0.70236052 state=CLOSING, > ts=1378296338838, server=bda1node01.etiya.com,60000,1378296027149 > > 1:54:37.227 PMINFOorg.apache.hadoop.hbase.master.AssignmentManager > > Region has been CLOSING for too long, this should eventually complete > or the server will expire, send RPC again > > > > > how to fix this problem? > > Thanks. >
