You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Konstantin Shvachko (JIRA)" <ji...@apache.org> on 2015/11/17 22:21:11 UTC
[jira] [Commented] (HDFS-7847) Modify NNThroughputBenchmark to be
able to operate on a remote NameNode
[ https://issues.apache.org/jira/browse/HDFS-7847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15009534#comment-15009534 ]
Konstantin Shvachko commented on HDFS-7847:
-------------------------------------------
Shouldn't we be specifying the namenode using the standard generic option {{-fs}}?
Also {{NNThroughputBenchmark}} was intended to benchmark NameNode's performance without RPC overhead.
There are other tools which can benchmark a real NameNode, like
- DFSIO,
- SLive,
- synthetic load generator or
I guess I did not fully understand your motivation here?
> Modify NNThroughputBenchmark to be able to operate on a remote NameNode
> -----------------------------------------------------------------------
>
> Key: HDFS-7847
> URL: https://issues.apache.org/jira/browse/HDFS-7847
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.8.0
> Reporter: Colin Patrick McCabe
> Assignee: Charles Lamb
> Fix For: 2.8.0
>
> Attachments: HDFS-7847.000.patch, HDFS-7847.001.patch, HDFS-7847.002.patch, HDFS-7847.003.patch, HDFS-7847.004.patch, HDFS-7847.005.patch, make_blocks.tar.gz
>
>
> Modify NNThroughputBenchmark to be able to operate on a NN that is not in process. A followon Jira will modify it some more to allow quantifying native and java heap sizes, and some latency numbers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)