Details
-
Sub-task
-
Status: Closed
-
Blocker
-
Resolution: Fixed
-
0.90.3
-
None
-
None
-
Reviewed
Description
The current implementation of the TimeoutMonitor acts like a race condition generator, mostly making things worse rather than better. It does it's own thing for a while without caring for what's happening in the rest of the master.
The first thing that needs to happen is that the regions should not be processed in one big batch, because that sometimes can take minutes to process (meanwhile a region that timed out opening might have opened, then what happens is it will be reassigned by the TimeoutMonitor generating the never ending PENDING_OPEN situation).
Those operations should also be done more atomically, although I'm not sure how to do it in a scalable way in this case.
Attachments
Attachments
Issue Links
- incorporates
-
HBASE-4203 While master restarts and if the META region's state is OPENING then master cannot assign META until timeout monitor deducts
- Closed