[
https://issues.apache.org/jira/browse/HDFS-4254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507952#comment-13507952
]
Hudson commented on HDFS-4254:
------------------------------
Integrated in Hadoop-Hdfs-0.23-Build #452 (See
[https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/452/])
HDFS-4254. testAllEditsDirsFailOnFlush makes subsequent test cases fail
(0.23.6 only) (Kihwal Lee via daryn) (Revision 1415899)
Result = SUCCESS
daryn : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1415899
Files :
*
/hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
/hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestEditLogJournalFailures.java
> testAllEditsDirsFailOnFlush makes subsequent test cases fail (0.23.6 only)
> --------------------------------------------------------------------------
>
> Key: HDFS-4254
> URL: https://issues.apache.org/jira/browse/HDFS-4254
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: test
> Affects Versions: 0.23.6
> Reporter: Kihwal Lee
> Assignee: Kihwal Lee
> Fix For: 0.23.6
>
> Attachments: hdfs-4254.branch-0.23.patch
>
>
> This jira is about a broken test case in branch-0.23 only.
> After HDFS-4233, testAllEditsDirsFailOnFlush started making subsequent cases
> in the same file fail. This is because MiniDFSCluster won't shutdown cleanly
> due to logSync() failure caused by lack of active journal streams. Without
> HDFS-4233, the condition was not detected and logSync() incorrectly ran
> without any error. To make MiniDFSCluster shutdown cleanly after a crash, the
> edit log needs to be aborted.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
