You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Lars George (JIRA)" <ji...@apache.org> on 2013/05/02 09:38:15 UTC
[jira] [Commented] (HBASE-8481) Add cost tracking to API calls for
resource management
[ https://issues.apache.org/jira/browse/HBASE-8481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647366#comment-13647366 ]
Lars George commented on HBASE-8481:
------------------------------------
I am planning to use this for my little night time project called Valta (https://github.com/larsgeorge/valta) to be able to do resource management in multitenant setups. Eventually we will need a more global resource management API controlling the RPC stack with its various pools (see http://www.eecs.berkeley.edu/Pubs/TechRpts/2012/EECS-2012-208.html). Valta - for now - is about controlling only clients within HBase, it is lacking the cross use-case facilities (interactive vs. batch usage, and HBase vs native HDFS usage).
> Add cost tracking to API calls for resource management
> ------------------------------------------------------
>
> Key: HBASE-8481
> URL: https://issues.apache.org/jira/browse/HBASE-8481
> Project: HBase
> Issue Type: New Feature
> Reporter: Lars George
>
> All calls that require resource should be tracked internally using a lightweight mechanism, such as a simple counter record. The idea is to be able to tell from calls how many resources they did require, for example a Get or Scan, how much true I/O was used. This should then be exposed to the Coprocessor context so that a plugin can make cost based decisions going forward with other calls. The record should include custom tags that in the preXYZ() calls can be used to for example tag a record with a user group and therefore be able to aggregate the statistics and accounting for groups of users.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira