Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
3.0.0-alpha-1, 2.3.0, 1.6.0
-
None
-
None
-
Reviewed
Description
We noticed a possible resource leak here. close() is called on reader at line 228 but if an I/O error occurs at line 225, reader remains open since the exception isn't caught locally.
I'll submit a pull request to fix it.
Attachments
Issue Links
- Parent Feature
-
HBASE-23073 Add an optional costFunction to balance regions according to a capacity rule
- Resolved
- links to