hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-931) Failing DFSOutputStream does not throw exception back to client
Date Fri, 29 Jan 2010 04:35:34 GMT

    [ https://issues.apache.org/jira/browse/HDFS-931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12806224#action_12806224
] 

Todd Lipcon commented on HDFS-931:
----------------------------------

This turns out to be a bit of a different bug/feature. The test case was using fs.close()
in order to implicitly close the stream. This caused the stream to flush on close, which is
where the errors occurred. Since LeaseChecker.close swallows exceptions, it never threw.

Is there a reason that LeaseChecker.close does not rethrow these exceptions as a MultipleIOException?

> Failing DFSOutputStream does not throw exception back to client
> ---------------------------------------------------------------
>
>                 Key: HDFS-931
>                 URL: https://issues.apache.org/jira/browse/HDFS-931
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs client
>    Affects Versions: 0.21.0, 0.22.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Blocker
>         Attachments: hdfs-931.txt, TEST-org.apache.hadoop.hdfs.TestFiPipelines.txt
>
>
> I've written a fault injection test that simply throws exceptions on every ack.readFields
call in ResponseProcessor. This ought to raise an exception to the client trying to use the
stream, but instead it ignores it silently.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message