[
https://issues.apache.org/jira/browse/HBASE-21672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16737513#comment-16737513
]
Sean Busbey commented on HBASE-21672:
-------------------------------------
Here's my concern: as an operator why should I have to know this detail of the
implementation? this is effectively a hidden "magically go faster" button. why
can't this be something that we take care of for the operator? Either by
whitelisting FileSystems that should skip it or pushing the providers of those
FileSystems to implement something that tells us as a downstream user that
there isn't going to be locality? Or doing a start up check that tells us there
isn't going to be locality (e.g. for the case where we are talking to HDFS but
that HDFS is a distinct set of nodes from our HBase nodes)?
> Allow skipping HDFS block distribution computation
> --------------------------------------------------
>
> Key: HBASE-21672
> URL: https://issues.apache.org/jira/browse/HBASE-21672
> Project: HBase
> Issue Type: Improvement
> Reporter: Nihal Jain
> Assignee: Nihal Jain
> Priority: Major
> Labels: S3
>
> We should have a configuration to skip HDFS block distribution calculation in
> HBase. For example on file systems that do not surface locality such as S3,
> calculating block distribution would not be any useful.
> Currentlly, we do not have a way to skip hdfs block distribution computation.
> For this, we can provide a new configuration key, say
> {{hbase.block.distribution.skip.computation}} (which would be {{false}} by
> default).
> Users using filesystems such as s3 may choose to make this {{true}}, thus
> skipping block distribution computation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
