You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Konstantin Boudnik (JIRA)" <ji...@apache.org> on 2014/02/28 21:48:20 UTC

[jira] [Comment Edited] (BIGTOP-1234) TestFileAppend should use a new client during testMultipleOutputStreamFailure()

    [ https://issues.apache.org/jira/browse/BIGTOP-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13916353#comment-13916353 ] 

Konstantin Boudnik edited comment on BIGTOP-1234 at 2/28/14 8:47 PM:
---------------------------------------------------------------------

Patched attached. Passed both vanilla cluster and multi-namenode cluster.


was (Author: virginia wang):
Patched attached. Passed both vanilla cluster and NSNN cluster.

> TestFileAppend should use a new client during testMultipleOutputStreamFailure()
> -------------------------------------------------------------------------------
>
>                 Key: BIGTOP-1234
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1234
>             Project: Bigtop
>          Issue Type: Bug
>          Components: Tests
>    Affects Versions: 0.7.0
>            Reporter: Virginia Wang
>            Assignee: Virginia Wang
>             Fix For: 0.8.0
>
>         Attachments: BIGTOP-1234.patch
>
>
> For a multiple namenode scenario testMultipleOutputStreamFailure() should fail when trying to open a second output stream while previous file is still opened. 
> The test can be modified to create a new DFSClient and perform the 2nd append call using the new client instead. 



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)