You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Gary Helmling (JIRA)" <ji...@apache.org> on 2013/12/17 00:28:08 UTC

[jira] [Commented] (HBASE-10170) Coprocessor task monitor

    [ https://issues.apache.org/jira/browse/HBASE-10170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849863#comment-13849863 ] 

Gary Helmling commented on HBASE-10170:
---------------------------------------

This patch introduces a whole new RPC server and whole new client, which seems like a large architectural change.  Can you please include a design / architecture document describing how this fits in with existing HBase architecture and how you expect it to be used?

Also please post the patch at reviews.apache.org to make it easier to review.

> Coprocessor task monitor
> ------------------------
>
>                 Key: HBASE-10170
>                 URL: https://issues.apache.org/jira/browse/HBASE-10170
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Coprocessors
>    Affects Versions: 0.99.0
>            Reporter: Jingcheng Du
>            Assignee: Jingcheng Du
>         Attachments: HBASE-10170.patch
>
>
> The coprocessor tasks are managed by the TaskMonitor in the server side. Usually these tasks run in a random long time, it’s hard to know how many tasks and how about the task status in the HRegionServer in the client side. 
> To add the client API for the coprocessor task monitor could improve that. Users could find the coprocessor task status by categories(coprocessor, client, user name, etc.), this is helpful to improve the lives of the operations guys who have to run HBase in production by giving them an API that can integrate HBase server and coprocessor task monitoring with Nagios etc.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)