[
https://issues.apache.org/jira/browse/HDFS-2011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13060812#comment-13060812
]
Todd Lipcon commented on HDFS-2011:
-----------------------------------
In the HDFS-1073 branch, EditLogOutputStream now has separate close() and
abort() methods. abort() is used when there has been some error on the stream
and we expect to do an "unclean" close (ie without flushing). close() is used
for clean closes. If close() itself fails, it will then proceed to abort() when
the IO error is handled.
So, I think the correct test case on the branch is to call abort() twice and
make sure that's ignored, or call close() and then abort() to make sure that's
ignored. Does that sound reasonable?
> Removal and restoration of storage directories on checkpointing failure
> doesn't work properly
> ---------------------------------------------------------------------------------------------
>
> Key: HDFS-2011
> URL: https://issues.apache.org/jira/browse/HDFS-2011
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 0.23.0
> Reporter: Ravi Prakash
> Assignee: Ravi Prakash
> Fix For: 0.23.0
>
> Attachments: HDFS-2011.3.patch, HDFS-2011.4.patch, HDFS-2011.5.patch,
> HDFS-2011.6.patch, HDFS-2011.7.patch, HDFS-2011.8.patch, HDFS-2011.patch,
> HDFS-2011.patch, HDFS-2011.patch
>
>
> Removal and restoration of storage directories on checkpointing failure
> doesn't work properly. Sometimes it throws a NullPointerException and
> sometimes it doesn't take off a failed storage directory
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
