My guess is HDFS-988 caused the slowdown by coarsening some locking that was
previously incorrect. Your stress test is NN-only (metadata ops), not an I/O
benchmark, right? I/O should be faster in trunk than ever before.
-Todd
On Fri, Jul 1, 2011 at 8:23 AM, Eric Payne wrote:
> Hi gang,
>
> I ra
[
https://issues.apache.org/jira/browse/HDFS-2122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ravi Prakash resolved HDFS-2122.
Resolution: Invalid
> Using the hadoop-deamon.sh script to start nodes leads to a depricated
> warn
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/998/
---
(Updated 2011-07-01 20:34:17.116645)
Review request for hadoop-hdfs, Dhruba Borth
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/998/
---
Review request for hadoop-hdfs, Dhruba Borthakur and Hairong Kuang.
Summary
-
Hi gang,
I ran some stress tests on the latest HDFS trunk yesterday, and the performance
is a lot slower (sometimes 10 times slower) when compared with the HDFS in
MR-279. The HDFS in MR-279 is slightly behind trunk. The stability of
HDFSÂ trunk
seems to be better than HDFS MR-279, but I'm not
Hi all,
I ran some stress tests on the latest HDFS trunk yesterday, and the performance
is a lot slower (sometimes 10 times slower) when compared with the HDFS in
MR-279. The HDFS in MR-279 is slightly behind trunk. The stability of the
namenode in trunk seems to be better than in MR-279 (speci
Using the hadoop-deamon.sh script to start nodes leads to a depricated warning
---
Key: HDFS-2122
URL: https://issues.apache.org/jira/browse/HDFS-2122
Project: Hadoop HDFS
