[
https://issues.apache.org/jira/browse/HDFS-16270?focusedWorklogId=665719&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-665719
]
ASF GitHub Bot logged work on HDFS-16270:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 14/Oct/21 15:17
Start Date: 14/Oct/21 15:17
Worklog Time Spent: 10m
Work Description: tomscut commented on pull request #3547:
URL: https://github.com/apache/hadoop/pull/3547#issuecomment-943459371
> In the results of jenkins, there are some exceptions, such as:
TestHDFSFileSystemContract TestLeaseRecovery TestFileTruncate
TestBlockTokenWithDFSStriped TestViewDistributedFileSystemWithMountLinks After
analysis, it does not seem to have much connection with the code I submitted.
>
> @tomscut @prasad-acit , would you like to spend some time to help review
this pr. Thank you very much.
Hi @jianghuazhu , sorry for the late reply.
IMO, there's nothing wrong with this hint.
Because when you specify the remote namenode with ```-fs```, if you do not
set ```dfs.namenode.fs-limits.min-block-size=16``` (because default
```BLOCK_SIZE = 16```), the default value of
```dfs.namenode.fs-limits.min-block-size``` on remote namenode will be
1024*1024 -> 1048576, and which will causes the following exception.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 665719)
Time Spent: 1h (was: 50m)
> Improve NNThroughputBenchmark#printUsage() related to block size
> ----------------------------------------------------------------
>
> Key: HDFS-16270
> URL: https://issues.apache.org/jira/browse/HDFS-16270
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: benchmarks, namenode
> Reporter: JiangHua Zhu
> Assignee: JiangHua Zhu
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h
> Remaining Estimate: 0h
>
> When using the NNThroughputBenchmark test, if the usage is not correct, we
> will get some prompt messages.
> E.g:
> '
> If connecting to a remote NameNode with -fs option,
> dfs.namenode.fs-limits.min-block-size should be set to 16.
> 21/10/13 11:55:32 INFO util.ExitUtil: Exiting with status -1: ExitException
> '
> Yes, this way is good.
> However, the setting of'dfs.blocksize' has been completed before execution,
> for example:
> conf.setInt(DFSConfigKeys.DFS_BLOCK_SIZE_KEY, 16);
> We will still get the above prompt, which is wrong.
> At the same time, it should also be explained. The hint here should not be
> for'dfs.namenode.fs-limits.min-block-size', but should be'dfs.blocksize'.
> Because in the NNThroughputBenchmark construction,
> the'dfs.namenode.fs-limits.min-block-size' has been set to 0 in advance.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
