[
https://issues.apache.org/jira/browse/HBASE-4070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13134734#comment-13134734
]
stack commented on HBASE-4070:
------------------------------
Here was my last comment on the patch over on RB in response to Eugene's "Hi
Michael, As Ted mentioned, HServerInfo is deprecated (per
https://issues.apache.org/jira/browse/HBASE-1502)":
{code}
Michael Stack 5 days, 4 hours ago (October 19th, 2011, 11:34 p.m.)
Yes but that is not reason to shoe horn it in elsewhere (smile).
There is another server attribute that is currently without a home (webuiport)
and I think there are other a bunch of server attrbutes -- as opposed to server
load -- that servers might export and have aggregated over in the master and/or
used calculating cluster balance and the like.
We could let this patch go in as is or we could build the server attributes
mechanism -- ServerInfoV2 or json in regionserver znode, etc. -- and put stuff
like this in there.
{code}
I think it a little perverse passing loaded coprocessors as part of
HServerLoad. I opened HBASE-4660 to address it.
> [Coprocessors] Improve region server metrics to report loaded coprocessors to
> master
> ------------------------------------------------------------------------------------
>
> Key: HBASE-4070
> URL: https://issues.apache.org/jira/browse/HBASE-4070
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 0.90.3
> Reporter: Mingjie Lai
> Assignee: Eugene Koontz
> Fix For: 0.92.0, 0.94.0
>
> Attachments: HBASE-4070.patch, HBASE-4070.patch, HBASE-4070.patch,
> HBASE-4070.patch, master-web-ui.jpg, rs-status-web-ui.jpg
>
>
> HBASE-3512 is about listing loaded cp classes at shell. To make it more
> generic, we need a way to report this piece of information from region to
> master (or just at region server level). So later on, we can display the
> loaded class names at shell as well as web console.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
