Affects Version/s: 0.90.2
Fix Version/s: 0.90.3
As I was talking in
HBASE-3669, it is really easy with the current RIT timeout to end up in situations where regions are doubly assigned, not assigned at all or assigned but the master doesn't know about it. As a bandaid, we should set hbase.master.assignment.timeoutmonitor.timeout to what the ZK session timeout is.
We had to do that to one of our clusters to be able to start it, else the master kept racing with itself.
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Resolution||Fixed [ 1 ]|
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|20h||1||Jean-Daniel Cryans||03/May/11 18:46|