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 Thu, 27 Oct 2016 01:17:58 GMT

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

binlijin commented on HBASE-16398:

We also run this patch on our production, and not have time to check the performance in production,
and waiting Enis Soztutar to comment on this, if there are some other committers review it,
i can continue finish it.

> 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
> 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