For people who don't want to restart the whole cluster, I have solved the
problem by restarting master alone and manually cleaning the table's ZK
state.
Thanks Jia for the suggestion of restarting master alone.
Thanks,
Yi
On Fri, Aug 5, 2011 at 5:35 PM, Yi Liang wrote:
> Looks like the issue o
Looks like the issue of HBASE-4064.
Hope it will be fixed ASAP. But for now, how can I fix the issue?
Due to the region in transition forever, the hbase balancer doesn't work any
more.
I have tried to kill and restart master alone, but it doesn't help. Do we
have to restart the whole cluster for
HI J-D,
I have tried to force unassign it with shell command 'unassign
HistoryNoticeInc,,1311223940614.aaa8d345f5b7b6a69b786fe6d14ed9fa.', true',
but it didn't help.
The error message still appears after executing that command, and it looks
like just same as before:
2011-08-04 09:56:41,005 DEBUG
You need to force unassign it using the shell.
J-D
On Mon, Aug 1, 2011 at 12:33 AM, Yi Liang wrote:
> We're running hbase 0.90.3. For some unknown reason, we now can't disable
> one table because its first region can't be unassigned.
>
> The log message looks like following and it repeats endles
We're running hbase 0.90.3. For some unknown reason, we now can't disable
one table because its first region can't be unassigned.
The log message looks like following and it repeats endlessly:
2011-07-25 13:27:23,745 INFO
org.apache.hadoop.hbase.master.AssignmentManager: Regions in transition
tim
