[jira] [Created] (HBASE-26729) Backport "HBASE-26714 Introduce path configuration for system coprocessors" to branch-2

[Tak-Lon (Stephen) Wu (Jira)]

Tak-Lon (Stephen) Wu created HBASE-26729:


 Summary: Backport "HBASE-26714 Introduce path configuration for 
system coprocessors" to branch-2
 Key: HBASE-26729
 URL: https://issues.apache.org/jira/browse/HBASE-26729
 Project: HBase
  Issue Type: Bug
  Components: Coprocessors
Affects Versions: 2.5.0
Reporter: Tak-Lon (Stephen) Wu


backport HBASE-26714 to branch-2, mainly it's due to the unclear cherry pick of 
the change of HBaseCommonTestUtility to HBaseCommonTestingUtility



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Created] (HBASE-26730) Extend hbase shell 'status' command to support an option 'tasks'

[Andrew Kyle Purtell (Jira)]

Andrew Kyle Purtell created HBASE-26730:
---

 Summary: Extend hbase shell 'status' command to support an option 
'tasks'
 Key: HBASE-26730
 URL: https://issues.apache.org/jira/browse/HBASE-26730
 Project: HBase
  Issue Type: Improvement
  Components: Operability, shell
Reporter: Andrew Kyle Purtell
Assignee: Andrew Kyle Purtell
 Fix For: 2.5.0, 2.6.0, 3.0.0-alpha-3
 Attachments: Screen Shot 2022-02-03 at 5.57.26 PM.png

Extend status command to support an option 'tasks', which will iterate over 
live regionservers and pretty print the status of any active MonitoredTasks.

1. Expose monitored tasks state in ClusterStatus API via new option in 
ServerLoad

2. Add shell support for interrogating monitored tasks state in ServerLoad




--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Resolved] (HBASE-26714) Introduce path configuration for system coprocessors

[Tak-Lon (Stephen) Wu (Jira)]

 [ 
https://issues.apache.org/jira/browse/HBASE-26714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tak-Lon (Stephen) Wu resolved HBASE-26714.
--
Release Note: After HBASE-26714, users of hbase can now set system 
coprocessor with a path of the JAR file other than the files in default 
classpath. E.g. when setting 
hbase.coprocessor.region.classes/hbase.coprocessor.regionserver.classes/hbase.coprocessor.user.region.classes/hbase.coprocessor.master.classes,
 user can set a comma-separated list with the format of 
className|priority|path, where the path could be a file path of the supported 
filesystem. 
Tags: coprocessors
  Resolution: Fixed

we will have the backport to branch-2 in HBASE-26729

> Introduce path configuration for system coprocessors
> 
>
> Key: HBASE-26714
> URL: https://issues.apache.org/jira/browse/HBASE-26714
> Project: HBase
>  Issue Type: Task
>  Components: Coprocessors
>Affects Versions: 2.5.0, 3.0.0-alpha-3
>Reporter: Tak-Lon (Stephen) Wu
>Assignee: Tak-Lon (Stephen) Wu
>Priority: Major
> Fix For: 3.0.0-alpha-3
>
>
> 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.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)