hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "George Porter (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-4096) Support for options within the Datanode Transfer protocol
Date Sat, 06 Sep 2008 02:02:44 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-4096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

George Porter updated HADOOP-4096:
----------------------------------

    Description: 
This proposal is to extend the DataNode Transfer protocol (described in DataNode.java lines
916 - 995) 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.

  was:
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.

        Summary: Support for options within the Datanode Transfer protocol  (was: Support
for options within the inter-datanode protocol)

Fixed terminology in the title

> Support for options within the Datanode Transfer 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 DataNode Transfer protocol (described in DataNode.java
lines 916 - 995) 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.


Mime
View raw message