[
https://issues.apache.org/jira/browse/HADOOP-9683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daryn Sharp updated HADOOP-9683:
--------------------------------
Resolution: Fixed
Fix Version/s: 2.3.0
2.1.0-beta
3.0.0
Release Note: Connection context is now sent as a rpc header wrapped
protobuf.
Hadoop Flags: Incompatible change,Reviewed (was: Incompatible change)
Status: Resolved (was: Patch Available)
Thanks Sanjay! I've committed to trunk & branch-2/2.1.
> Wrap IpcConnectionContext in RPC headers
> ----------------------------------------
>
> Key: HADOOP-9683
> URL: https://issues.apache.org/jira/browse/HADOOP-9683
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: ipc
> Reporter: Luke Lu
> Assignee: Daryn Sharp
> Priority: Blocker
> Fix For: 3.0.0, 2.1.0-beta, 2.3.0
>
> Attachments: HADOOP-9683.branch-2.patch, HADOOP-9683.patch,
> HADOOP-9683.trunk.patch
>
>
> After HADOOP-9421, all RPC exchanges (including SASL) are wrapped in RPC
> headers except IpcConnectionContext, which is still raw protobuf, which makes
> request pipelining (a desirable feature for things like HDFS-2856) impossible
> to achieve in a backward compatible way. Let's finish the job and wrap
> IpcConnectionContext with the RPC request header with the call id of
> SET_IPC_CONNECTION_CONTEXT. Or simply make it an optional field in the RPC
> request header that gets set for the first RPC call of a given stream.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
