Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
Reviewed
-
Description
Continuing where HBASE-10015 left of.
We can avoid locking (and memory fencing) inside StoreScanner by deferring to the lock already held by the RegionScanner.
In tests this shows quite a scan improvement and reduced CPU (the fences make the cores wait for memory fetches).
There are some drawbacks too:
- All calls to RegionScanner need to be remain synchronized
- Implementors of coprocessors need to be diligent in following the locking contract. For example Phoenix does not lock RegionScanner.nextRaw() and required in the documentation (not picking on Phoenix, this one is my fault as I told them it's OK)
- possible starving of flushes and compaction with heavy read load. RegionScanner operations would keep getting the locks and the flushes/compactions would not be able finalize the set of files.
I'll have a patch soon.
Attachments
Attachments
Issue Links
- is related to
-
HBASE-20704 Sometimes some compacted storefiles are not archived on region close
- Closed
- relates to
-
HBASE-18186 Frequent FileNotFoundExceptions in region server logs
- Closed
-
HBASE-14970 Backport HBASE-13082 and its sub-jira to branch-1
- Closed
-
HBASE-10060 Unsynchronized scanning
- Closed
-
HBASE-13071 Hbase Streaming Scan Feature
- Closed
-
HBASE-13090 Progress heartbeats for long running scanners
- Closed
- links to