[
https://issues.apache.org/jira/browse/HDFS-16270?focusedWorklogId=664469&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-664469
]
ASF GitHub Bot logged work on HDFS-16270:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 13/Oct/21 06:04
Start Date: 13/Oct/21 06:04
Worklog Time Spent: 10m
Work Description: jianghuazhu opened a new pull request #3547:
URL: https://github.com/apache/hadoop/pull/3547
### Description of PR
When NNThroughputBenchmark#printUsage() is executed, some configurations are
verified first, and the correct prompts are printed.
### How was this patch tested?
This is to print some information, the test pressure is not great.
--
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: 664469)
Remaining Estimate: 0h
Time Spent: 10m
> 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
> Time Spent: 10m
> 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]
