You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Kannan Muthukkaruppan (JIRA)" <ji...@apache.org> on 2012/06/15 19:20:42 UTC
[jira] [Created] (HBASE-6216) per-request tagging
Kannan Muthukkaruppan created HBASE-6216:
--------------------------------------------
Summary: 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: Kannan Muthukkaruppan
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).
--
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
[jira] [Assigned] (HBASE-6216) per-request tagging
Posted by "Kannan Muthukkaruppan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kannan Muthukkaruppan reassigned HBASE-6216:
--------------------------------------------
Assignee: Aurick Qiao (was: Kannan Muthukkaruppan)
accidentally assigned the wrong JIRA to Michael.
> 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).
--
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
[jira] [Updated] (HBASE-6216) per-request tagging
Posted by "Kannan Muthukkaruppan (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (HBASE-6216) per-request tagging
Posted by "Li Pi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443802#comment-13443802 ]
Li Pi commented on HBASE-6216:
------------------------------
Patch: https://reviews.facebook.net/D5007
> 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: Li Pi
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6216) per-request tagging
Posted by "Li Pi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443803#comment-13443803 ]
Li Pi commented on HBASE-6216:
------------------------------
I should probably modify the SchemaMetrics test cases to test for tags as well.
> 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: Li Pi
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HBASE-6216) per-request tagging
Posted by "Kannan Muthukkaruppan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kannan Muthukkaruppan reassigned HBASE-6216:
--------------------------------------------
Assignee: Kannan Muthukkaruppan (was: M. Chen)
> 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: Kannan Muthukkaruppan
>
> 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).
--
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
[jira] [Assigned] (HBASE-6216) per-request tagging
Posted by "Li Pi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Li Pi reassigned HBASE-6216:
----------------------------
Assignee: Li Pi (was: Aurick Qiao)
> 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: Li Pi
>
> 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
[jira] [Assigned] (HBASE-6216) per-request tagging
Posted by "Kannan Muthukkaruppan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kannan Muthukkaruppan reassigned HBASE-6216:
--------------------------------------------
Assignee: M. Chen (was: Aurick Qiao)
> 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: M. Chen
>
> 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).
--
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
[jira] [Assigned] (HBASE-6216) per-request tagging
Posted by "Kannan Muthukkaruppan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kannan Muthukkaruppan reassigned HBASE-6216:
--------------------------------------------
Assignee: Aurick Qiao (was: Kannan Muthukkaruppan)
> 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).
--
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