haosdent created HDFS-5356:
--
Summary: MiniDFSCluster shoud close all open FileSystems when
shutdown()
Key: HDFS-5356
URL: https://issues.apache.org/jira/browse/HDFS-5356
Project: Hadoop HDFS
Issue
haosdent created HDFS-5355:
--
Summary: Hsync Metrics error
Key: HDFS-5355
URL: https://issues.apache.org/jira/browse/HDFS-5355
Project: Hadoop HDFS
Issue Type: Bug
Reporter: haosdent
haosdent created HDFS-5354:
--
Summary: testHDFSConf.xml assumes username is composed by
[a-zA-z0-9]
Key: HDFS-5354
URL: https://issues.apache.org/jira/browse/HDFS-5354
Project: Hadoop HDFS
Issue
I still couldn't see the image. The page shows that "The page you requested
could not be found.".
--
Best Regards,
Haosong Huang
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
On Monday, October 7, 2013 at 12:38 PM, 남윤민 wrote:
> Here is image I uploaded.
>
> Sorry for that!
>
> h
ly* want to be sure, pay the cost of hsync and do
> durable writes.
>
>
> On Sun, Aug 25, 2013 at 7:44 PM, haosdent (mailto:haosd...@gmail.com)> wrote:
>
> > In fact, I just write 4k in every hsync. Datenode would write checksum
> > file and data file when I hsync dat
= 4MB
>
> If you're hsync'ing every 4MB, 50ms would be exactly what I'd expect.
>
> Best,
> Andrew
>
>
> On Sat, Aug 24, 2013 at 10:11 PM, haosdent (mailto:haosd...@gmail.com)> wrote:
>
> > Hi, all. Hadoop support hsync which would call fsyn
Hi, all. Hadoop support hsync which would call fsync of system after 2.0.2. I
have tested the performance of hsync() and hflush() again and again, but I
found that the hsync call() everytime would spent nearly 50ms while the hflush
call() just spent 2ms. In this
slide(http://www.slideshare.net/
