[
https://issues.apache.org/jira/browse/HDFS-17272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17792387#comment-17792387
]
ASF GitHub Bot commented on HDFS-17272:
---------------------------------------
lfxy opened a new pull request, #6319:
URL: https://github.com/apache/hadoop/pull/6319
Currently, NNThroughputBenchmark does not support specifying the base
directory, therefore does not support multiple clients performing stress
testing at the same time. However, for high-performance namenode machine, only
one client submitting stress test can not make the namenode rpc access reach
the bottleneck. Therefore, multiple clients are required for parallel testing
to make the namenode pressure reach the level of the large-scale production
cluster.
So I specify the base directory through the -baseDirName parameter to
support multiple clients submitting stress tests at the same time.
> NNThroughputBenchmark should support specifying the base directory for
> multi-client test
> ----------------------------------------------------------------------------------------
>
> Key: HDFS-17272
> URL: https://issues.apache.org/jira/browse/HDFS-17272
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Affects Versions: 3.4.0
> Reporter: caozhiqiang
> Assignee: caozhiqiang
> Priority: Major
>
> Currently, NNThroughputBenchmark does not support specifying the base
> directory, therefore does not support multiple clients performing stress
> testing at the same time. However, for high-performance namenode machine,
> only one client submitting stress test can not make the namenode rpc access
> reach the bottleneck. Therefore, multiple clients are required for parallel
> testing to make the namenode pressure reach the level of the large-scale
> production cluster.
> So I specify the base directory through the -baseDirName parameter to support
> multiple clients submitting stress tests at the same time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
