hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3398) Client will not retry when primaryDN is down once it's just got pipeline
Date Tue, 29 May 2012 19:48:23 GMT

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

Hudson commented on HDFS-3398:
------------------------------

Integrated in Hadoop-Common-trunk-Commit #2298 (See [https://builds.apache.org/job/Hadoop-Common-trunk-Commit/2298/])
    HDFS-3398. Client will not retry when primaryDN is down once it's just got pipeline. Contributed
by Amith D K. (Revision 1343944)

     Result = SUCCESS
umamahesh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1343944
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSOutputStream.java

                
> Client will not retry when primaryDN is down once it's just got pipeline
> ------------------------------------------------------------------------
>
>                 Key: HDFS-3398
>                 URL: https://issues.apache.org/jira/browse/HDFS-3398
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs client
>    Affects Versions: 2.0.0-alpha
>            Reporter: Brahma Reddy Battula
>            Assignee: amith
>            Priority: Minor
>             Fix For: 2.0.1-alpha, 3.0.0
>
>         Attachments: HDFS-3398.patch, HDFS-3398.patch, HDFS_3398_3.patch
>
>
> Scenario:
> =========
> Start NN and three DN"S
> Get the datanode to which blocks has to be replicated.
> from 
> {code}
> nodes = nextBlockOutputStream(src);
> {code}
> Before start writing to the DN ,kill the primary DN.
> {code}
> // write out data to remote datanode
>           blockStream.write(buf.array(), buf.position(), buf.remaining());
>           blockStream.flush();
> {code}
> Now write will fail with the exception 
> {noformat}
> 2012-05-10 14:21:47,993 WARN  hdfs.DFSClient (DFSOutputStream.java:run(552)) - DataStreamer
Exception
> java.io.IOException: An established connection was aborted by the software in your host
machine
> 	at sun.nio.ch.SocketDispatcher.write0(Native Method)
> 	at sun.nio.ch.SocketDispatcher.write(Unknown Source)
> 	at sun.nio.ch.IOUtil.writeFromNativeBuffer(Unknown Source)
> 	at sun.nio.ch.IOUtil.write(Unknown Source)
> 	at sun.nio.ch.SocketChannelImpl.write(Unknown Source)
> 	at org.apache.hadoop.net.SocketOutputStream$Writer.performIO(SocketOutputStream.java:60)
> 	at org.apache.hadoop.net.SocketIOWithTimeout.doIO(SocketIOWithTimeout.java:142)
> 	at org.apache.hadoop.net.SocketOutputStream.write(SocketOutputStream.java:151)
> 	at org.apache.hadoop.net.SocketOutputStream.write(SocketOutputStream.java:112)
> 	at java.io.BufferedOutputStream.write(Unknown Source)
> 	at java.io.DataOutputStream.write(Unknown Source)
> 	at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.run(DFSOutputStream.java:513)
> {noformat}
> .

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message