You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Daryn Sharp (JIRA)" <ji...@apache.org> on 2013/09/09 20:17:52 UTC
[jira] [Commented] (HADOOP-9944) RpcRequestHeaderProto defines
callId as uint32 while ipc.Client.CONNECTION_CONTEXT_CALL_ID is signed (-3)
[ https://issues.apache.org/jira/browse/HADOOP-9944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13762118#comment-13762118 ]
Daryn Sharp commented on HADOOP-9944:
-------------------------------------
There are multiple negative callIds to signal out of band operations, such as ping and sasl. Is the intention to change the protobuf def to a signed int?
> 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
> Priority: Blocker
>
> 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