You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Raghu Angadi (JIRA)" <ji...@apache.org> on 2008/03/12 22:28:46 UTC
[jira] Updated: (HADOOP-3007) DataNode pipelining : failure on
mirror results in failure on upstream datanode
[ https://issues.apache.org/jira/browse/HADOOP-3007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Raghu Angadi updated HADOOP-3007:
---------------------------------
Description:
When datanode is transfering data to other datanodes (as opposed to a client write()), DN currently receiving the data is supposed to continued to receive even if the downstream (mirror) datanode fails.
I think there are two minor bugs in receiveBlock() :
# mirrorSock masks this.mirrorSock, which could be set to null by other members like receiveChunk() to indicate failure.
# when this.mirrorSock is non null, failure to write to it at in receiveBlock() should be handled same way as in receiveChunk().
I am not sure if this should block 0.16.1, but should surely block 0.16.2.
was:
When datanode is transfering data to other datanodes (as opposed to a client write()), DN currently receiving the data is supposed to continued to receive even if the downstream (mirror) datanode fails.
I think there are two minor bugs in receiveBlock() :
# mirrorSock masks this.mirrorSock, which could be set to null by other members like receiveChunk() to indicate failure.
# when this.mirrorSock is non null, failure to write to it at in receiveBlock() should be handled same way as in receiveChunk().
I am not sure if this should block 0.16.1, but should surely block 0.16.2.
Summary: DataNode pipelining : failure on mirror results in failure on upstream datanode (was: DataNode pipelining : failure on mirror make results in failure on upstream datanode)
> DataNode pipelining : failure on mirror results in failure on upstream datanode
> -------------------------------------------------------------------------------
>
> Key: HADOOP-3007
> URL: https://issues.apache.org/jira/browse/HADOOP-3007
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.16.0
> Reporter: Raghu Angadi
> Priority: Blocker
> Fix For: 0.16.2
>
>
> When datanode is transfering data to other datanodes (as opposed to a client write()), DN currently receiving the data is supposed to continued to receive even if the downstream (mirror) datanode fails.
> I think there are two minor bugs in receiveBlock() :
> # mirrorSock masks this.mirrorSock, which could be set to null by other members like receiveChunk() to indicate failure.
> # when this.mirrorSock is non null, failure to write to it at in receiveBlock() should be handled same way as in receiveChunk().
> I am not sure if this should block 0.16.1, but should surely block 0.16.2.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.