Details
-
Sub-task
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
3.0.0-alpha-1, 1.5.0, 2.3.0
-
None
-
None
Description
We can leak store reader references if a coprocessor or core function somehow opens a scanner, or wraps one, and then does not take care to call close on the scanner or the wrapped instance. A reasonable mitigation for a reader reference leak would be a fast reopen of the region on the same server (initiated by the RS) This will release all resources, like the refcount, leases, etc. The clients should gracefully ride over this like any other region transition. This reopen would be like what is done during schema change application and ideally would reuse the relevant code. If the refcount is over some ridiculous threshold this mitigation could be triggered along with a fat WARN in the logs.
Attachments
Issue Links
- breaks
-
HBASE-25147 Should store the regionNames field in state data for ReopenTableRegionsProcedure
- Resolved
- is a parent of
-
HBASE-23212 Provide config reload for Auto Region Reopen based on storeFile ref count
- Resolved
-
HBASE-23213 Backport HBASE-22460 to branch-1
- Resolved
- is related to
-
HBASE-23349 Low refCount preventing archival of compacted away files
- Resolved
- relates to
-
PHOENIX-5296 Ensure store file reader refcount is zero at end of relevant unit tests
- Resolved
- links to