Details
-
Bug
-
Status: Closed
-
Blocker
-
Resolution: Fixed
-
0.90.2
-
None
-
None
-
Reviewed
Description
HRegion maintains a set of row locks. Whenever any thread attempts to lock or release a row it needs to acquire the monitor on that set. We've been encountering cases with 30 handler threads all contending for that monitor, blocked progress on the region server. Clients timeout, and retry making it worse, and the region server stops responding to new clients almost entirely.
Attachments
Attachments
Issue Links
- is depended upon by
-
HBASE-3893 HRegion.internalObtainRowLock shouldn't wait forever
- Closed
- is related to
-
HBASE-2295 Row locks may deadlock with themselves
- Closed
-
HBASE-3893 HRegion.internalObtainRowLock shouldn't wait forever
- Closed