Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <1705534981.1220661164559.JavaMail.jira@brutus>
Date: Fri, 5 Sep 2008 17:32:44 -0700 (PDT)
From: "Tsz Wo (Nicholas), SZE (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-4096) Support for options within the
 inter-datanode protocol
In-Reply-To: <1949842487.1220657686216.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-4096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628803#action_12628803 ] 

Tsz Wo (Nicholas), SZE commented on HADOOP-4096:
------------------------------------------------

Do you mean "Datanode transfer protocol", i.e. the protocol described in DataNode.java line 916 - 995?  Inter-datanode protocol is another protocol defined in org.apache.hadoop.hdfs.server.protocol.InterDatanodeProtocol.

> Support for options within the inter-datanode protocol
> ------------------------------------------------------
>
>                 Key: HADOOP-4096
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4096
>             Project: Hadoop Core
>          Issue Type: New Feature
>          Components: dfs
>            Reporter: George Porter
>
> This proposal is to extend the streaming inter-datanode protocol to support "options", in the spirit of IP or TCP options.  This should make this protocol more extensible, allowing the client to include metadata along with commands.  This would support efforts to include end-to-end and causal tracing into Hadoop, and hopefully other efforts as well.
> Options should have a type, and be of variable length.  It should be possible to include multiple options along with each datanode command.  The option should apply to both the command and any data that is part of the command.  If the datanode does not understand a given option, it should ignore it.  Options should be sent end-to-end through intermediate datanodes, if necessary.  For example, if an OP_WRITE_BLOCK command is pipelined through several machines, the options should be sent along the pipeline.  Nodes along the pipeline may modify the options.
> BTW, If HADOOP-4005 (concrete datanode protocol) is implemented, then it should solve this problem by simply letting the user add state to the concrete protocol class.

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