Details
-
Task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.5.0, 3.0.0-alpha-3
-
None
-
-
coprocessors
Description
Currently when region server starts, system coprocessors are normally loaded as part of the local classpath and the jar is stored in the local storage; in short words, Operator would have to copy the jar to each host (or a shared file system) and construct it as part of HBASE_CLASSPATH.
although operator may have been doing the presetup of copying jar and making it available to the HBASE_CLASSPATH without any issue, it could be helpful if we provide an alternative method and centralize this configuration in hbase-site similar to the support of table-level coprocessor, e.g. configuring hbase.coprocessor.region.classes with the local/remote path along with the classname with a specific path token in the form of className|priority|path.
Similarly in HBASE-23710, it provided the priority configuration via hbase-site that this new improvement aligns with the same purpose, and further help to simplify the deployment of System Coprocessors to e.g. hdfs or supported cloud storage.
Attachments
Issue Links
- relates to
-
HBASE-26729 Backport "HBASE-26714 Introduce path configuration for system coprocessors" to branch-2
- Resolved
- links to