[
https://issues.apache.org/jira/browse/HBASE-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kannan Muthukkaruppan updated HBASE-6216:
-----------------------------------------
Description:
Allow applications to tag individual RPC requests so that metrics exposed by
HBase can automatically be collected/aggregated by those tags. This'll be
useful for problem diagnosis across various applications-- as it will allow us
to correlate HBase metrics (such as data block misses) back to application
level tags.
For example,
* in some multi-tenancy type use case where many different applications are
served out of a single Table or CF, it'll be useful to know the break down of
metrics (such as bytes read, data block misses, get/put RPC calls, etc.) by
application name (tag).
* even in a single app environment, the app may want to tag different API calls
with different tags even if those calls are to the same CF.
was:
Allow applications to tag individual RPC requests so that metrics exposed by
HBase can automatically be collected/aggregated by those tags. This'll be
useful for problem diagnosis across various applications-- as it will allow us
to correlate HBase metrics (such as data block misses) back to application
level tags.
For example, in some multi-tenancy type use case where many different
applications are served out of a single Table or CF, it'll be useful to know
the break down of metrics (such as bytes read, data block misses, get/put RPC
calls, etc.) by application name (tag).
> per-request tagging
> -------------------
>
> Key: HBASE-6216
> URL: https://issues.apache.org/jira/browse/HBASE-6216
> Project: HBase
> Issue Type: New Feature
> Reporter: Kannan Muthukkaruppan
> Assignee: Aurick Qiao
>
> Allow applications to tag individual RPC requests so that metrics exposed by
> HBase can automatically be collected/aggregated by those tags. This'll be
> useful for problem diagnosis across various applications-- as it will allow
> us to correlate HBase metrics (such as data block misses) back to application
> level tags.
> For example,
> * in some multi-tenancy type use case where many different applications are
> served out of a single Table or CF, it'll be useful to know the break down of
> metrics (such as bytes read, data block misses, get/put RPC calls, etc.) by
> application name (tag).
> * even in a single app environment, the app may want to tag different API
> calls with different tags even if those calls are to the same CF.
--
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
