[
https://issues.apache.org/jira/browse/HADOOP-9683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daryn Sharp updated HADOOP-9683:
--------------------------------
Attachment: HADOOP-9683.trunk.patch
HADOOP-9683.branch-2.patch
Patches are split now due to trunk having a new {{callId}} in the rpc header.
# Add call id to {{RpcConstants}} on trunk
# Increment connection context call id from -2 to -3 to avoid conflict with
{{InvalidCallId}}
# Instantiate protobuf just prior to sending to allow adding the new
{{clientId}} to the header
# Rename {{RpcReplyException}} to {{WrappedRpcServerException}}
# Change method signatures to be more precise - remove generic {{IOException}}
where possible
# Push the sending of {{saslResponse}} up in the call stack to allowal removal
of {{IOException}} from a few methods.
# Aforementioned changes exposed a few exceptions not being wrapped
# Update javadocs
> 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
> 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
