hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "binlijin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16398) optimize HRegion computeHDFSBlocksDistribution
Date Wed, 09 Nov 2016 06:55:59 GMT

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

binlijin commented on HBASE-16398:

Thanks very much for the perf benchmark, i run on one of our cluster(opentsdb cluster, tsdb
table have 5690 regions) and i can get the flowing result:
Batch mode of computation: 45 seconds
Old mode of computation: 70 seconds

> optimize HRegion computeHDFSBlocksDistribution
> ----------------------------------------------
>                 Key: HBASE-16398
>                 URL: https://issues.apache.org/jira/browse/HBASE-16398
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: binlijin
>            Assignee: binlijin
>         Attachments: HBASE-16398.patch, LocatedBlockStatusComparison.java
> First i assume there is no reference and link in a region family's directory. 
> Without the patch to computeHDFSBlocksDistribution for a region family, there is 1+2*N
rpc call, N is hfile numbers, The first rpc call is to DistributedFileSystem#listStatus to
get hfiles, for every hfile there is two rpc call DistributedFileSystem#getFileStatus(path)
and then DistributedFileSystem#getFileBlockLocations(status, start, length).
> With the patch to computeHDFSBlocksDistribution for a region family, there is 2 rpc call,
they are DistributedFileSystem#getFileStatus(path) and  DistributedFileSystem#listLocatedStatus(final
Path p, final PathFilter filter).
> So if there is at least one hfile, with the patch, the rpc call will less.

This message was sent by Atlassian JIRA

View raw message