Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
Reviewed
Description
We've standardized on IOException as the main way for coprocessors to communicate errors back out of the Observer hooks. All Observer hooks throw IOE except for MasterObserver.preMove() and MasterObserver.postMove(), which throw UnknownRegionException, since that's what HMasterInterface.move() declares. In hindsight, making these two MasterObserver methods inconsistent seems like a mistake.
I think we should change MasterObserver.preMove() and MasterObserver.postMove() to throw IOException for consistency with the other methods. We could deprecate the existing HMasterInterface.move() method to have it switch over to throwing IOException as well, but this would require creating a version with a new name, which seems unnecessarily ugly. So I'd suggest we just have HMaster.move() handle the IOException and use it to init an UnknownRegionException. Wonky as that is, it seems the lesser evil.
Attachments
Attachments
Issue Links
- is depended upon by
-
HBASE-4014 Coprocessors: Flag the presence of coprocessors in logged exceptions
- Closed