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

Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2011/04/01 19:40:06 UTC

[jira] [Commented] (HBASE-3647) Distinguish read and write request count in region

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

stack commented on HBASE-3647:
------------------------------

To be clear, for this patch to be committed, we will need to up our rpc version on all proxy interfaces.  HServerLoad is buried inside HServerInfo at the moment.  Its looking like pressure is building such that we will have to up our version numbers -- hbase-1502 where we rejigger heartbeat includes deprecation of HSA and redo of HSI -- but also Gary has patch to include cluster id in ClusterStatue....  So, the RPC version bump looks like it'll happen soon.  We'll apply this patch then.

> Distinguish read and write request count in region
> --------------------------------------------------
>
>                 Key: HBASE-3647
>                 URL: https://issues.apache.org/jira/browse/HBASE-3647
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Ted Yu
>            Assignee: Ted Yu
>             Fix For: 0.92.0
>
>         Attachments: hbase-3647.txt
>
>
> Distinguishing read and write request counts, on top of HBASE-3507, would benefit load balancer.
> The action for balancing read vs. write load should be different. For read load, region movement should be low (to keep scanner happy). For write load, region movement is allowed.
> Now that we have cheap(er) counters, it should not be too burdensome keeping up the extra count.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira