[
https://issues.apache.org/jira/browse/HADOOP-9683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13699289#comment-13699289
]
Hadoop QA commented on HADOOP-9683:
-----------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12590683/HADOOP-9683.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-common-project/hadoop-common.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/2730//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/2730//console
This message is automatically generated.
> 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.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
