[ https://issues.apache.org/jira/browse/HBASE-5256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13197475#comment-13197475 ]
stack commented on HBASE-5256: ------------------------------ Will we have to be careful with this patch? It can't go into a minor version, right else you could have a regionserver reporting a master metrics in a format it can't interpret (or vice versa, the master will be expecting them as longs but they come over as vlongs). We up the version on HServerLoad but don't exploit the version change. We could have had HSL self-migrate reading using old code if it got a v1 HSL to deserialize. Then we could have this in a point version. > Use WritableUtils.readVInt() in RegionLoad.readFields() > ------------------------------------------------------- > > Key: HBASE-5256 > URL: https://issues.apache.org/jira/browse/HBASE-5256 > Project: HBase > Issue Type: Task > Reporter: Zhihong Yu > Assignee: Mubarak Seyed > Fix For: 0.94.0 > > Attachments: HBASE-5256.trunk.v1.patch > > > Currently in.readInt() is used in RegionLoad.readFields() > More metrics would be added to RegionLoad in the future, we should utilize > WritableUtils.readVInt() to reduce the amount of data exchanged between > Master and region servers. -- 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