[
https://issues.apache.org/jira/browse/HADOOP-9944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13981984#comment-13981984
]
Charlene Sun commented on HADOOP-9944:
--------------------------------------
Hey Guys,
I discovered the callid for a request and its response do not always match
while writing a protocol analyzer to analyze application data. A simple test
case can demonstrate this problem:
An unauthorized access to a file which causes a client to send setOwner request
rpc to a Namenode server which in turn sends back the client a response
includes org.apache.hadoop.security.AccessControlException. And the callid of
the request and response doesn't match.
Could someone please take a look at this?
Thanks.
Charlene Sun
> 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 was sent by Atlassian JIRA
(v6.2#6252)
