[
https://issues.apache.org/jira/browse/HADOOP-9944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13769507#comment-13769507
]
Hudson commented on HADOOP-9944:
--------------------------------
FAILURE: Integrated in Hadoop-Mapreduce-trunk #1551 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1551/])
HADOOP-9944. Fix RpcRequestHeaderProto.callId to be sint32 rather than uint32
since ipc.Client.CONNECTION_CONTEXT_CALL_ID is signed (i.e. -3). Contributed by
Arun C. Murthy. (acmurthy:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1523885)
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/proto/ProtobufRpcEngine.proto
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/proto/RpcHeader.proto
> RpcRequestHeaderProto defines callId as uint32 while
> ipc.Client.CONNECTION_CONTEXT_CALL_ID is signed (-3)
> ---------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-9944
> URL: https://issues.apache.org/jira/browse/HADOOP-9944
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Arun C Murthy
> Assignee: Arun C Murthy
> Priority: Blocker
> Fix For: 2.1.1-beta
>
> Attachments: HADOOP-9944.patch, HADOOP-9944.patch, HADOOP-9944.patch
>
>
> RpcRequestHeaderProto defines callId as uint32 while
> ipc.Client.CONNECTION_CONTEXT_CALL_ID is signed (-3).
--
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
