[
https://issues.apache.org/jira/browse/HADOOP-8422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281613#comment-13281613
]
Harsh J commented on HADOOP-8422:
---------------------------------
bq. Out of curiousity, why is HBase querying the default block size?
One thing I am aware of is that it relies on default HDFS block sizes as the
default threshold for HLog rolls. This value is presently loaded (for a checker
thread) before a HLog is created so there's no path at that point. HBase can be
fixed to use a path.
MR2 tasks too query HDFS block size presently to determine (versus the input
size of a job) if a task can be made uber. MR2 does use a Path though (job
submission directory presently, although thats wrong and there's a FIXME in
there to use the input file instead…).
I do not quite know what ViewFileSystem does at the moment, but for non-Path
queries is there no View-Root-Path it can fall back on?
> FileSystem#getDefaultBlockSize and Replication don't use the given path
> -----------------------------------------------------------------------
>
> Key: HADOOP-8422
> URL: https://issues.apache.org/jira/browse/HADOOP-8422
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Affects Versions: 1.0.3
> Reporter: Eli Collins
> Priority: Minor
>
> The javadocs for FileSystem#getDefaultBlockSize and
> FileSystem#getDefaultReplication claim that "The given path will be used to
> locate the actual filesystem" however they both ignore the path.
--
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
