[ https://issues.apache.org/jira/browse/HDFS-6773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14109982#comment-14109982 ]
Stephen Chu commented on HDFS-6773: ----------------------------------- It looks like the hdfs test run was aborted, but I'm not exactly sure why. I reapplied the patch to a clean trunk and ran some snapshot tests successfully to double-check. Re-triggering Hadoop QA. > MiniDFSCluster should skip edit log fsync by default > ---------------------------------------------------- > > Key: HDFS-6773 > URL: https://issues.apache.org/jira/browse/HDFS-6773 > Project: Hadoop HDFS > Issue Type: Improvement > Components: namenode > Affects Versions: 2.0.0-alpha, 3.0.0 > Reporter: Daryn Sharp > Assignee: Stephen Chu > Attachments: HDFS-6773.1.patch, HDFS-6773.2.patch > > > The mini cluster is unnecessarily running with durable edit logs. The > following change cut runtime of a single test from ~30s to ~10s. > {code}EditLogFileOutputStream.setShouldSkipFsyncForTesting(true);{code} > The mini cluster should default to this behavior after identifying the few > edit log tests that probably depend on durable logs. -- This message was sent by Atlassian JIRA (v6.2#6252)