欢迎访问 生活随笔!

生活随笔

当前位置: 首页 > 编程资源 > 编程问答 >内容正文

编程问答

Hadoop RPC protocol description--转

发布时间:2025/4/5 编程问答 70 豆豆
生活随笔 收集整理的这篇文章主要介绍了 Hadoop RPC protocol description--转 小编觉得挺不错的,现在分享给大家,帮大家做个参考.

原文地址:https://spotify.github.io/snakebite/hadoop_rpc.html

Snakebite currently implements the following protocol in snakebite.channel.SocketRpcChannel to communicate with the NameNode.

Connection

The Hadoop RPC protocol works as described below. On connection, headers are sent to setup a session. After that, multiple requests can be sent within the session.

FunctionTypeDefault
Headerbytes“hrpc”
Versionuint87
Auth methoduint880 (Auth method SIMPLE)
Serialization typeuint80 (protobuf)
IpcConnectionContextProto lengthuint32 
IpcConnectionContextProtobytes 

Sending messages

When sending a message, the following is sent to the sever:

FunctionType
Length of the next two partsuint32
RpcPayloadHeaderProto lengthvarint
RpcPayloadHeaderProtoprotobuf serialized message
HadoopRpcRequestProto lengthvarint
HadoopRpcRequestProtoprotobuf serialized message

varint is a Protocol Buffer variable int.

Note

The Java protobuf implementation uses writeToDelimited to prepend the message with their lenght, but the python implementation doesn’t implement such a method (yet).

Next to an rpcKind (snakebites default is RPC_PROTOCOL_BUFFER), an rpcOp (snakebites default isRPC_FINAL_PAYLOAD), the RpcPayloadHeaderProto message defines a callId that is added in the RPC response (described below).

The HadoopRpcRequestProto contains a methodName field that defines what server method is called and a has a property request that contains the serialized actual request message.

Receiving messages

After a message is sent, the response can be read in the following way:

FunctionType
Length of the RpcResponseHeaderProtovarint
RpcResponseHeaderProtobytes
Length of the RPC responseuint32
Serialized RPC responsebytes

The RpcResponseHeaderProto contains the callId of the request and a status field. The status can beSUCCESSERROR or FAILURE. In case SUCCESS the rest of response is a complete protobuf response.

In case of ERROR, the response looks like follows:

FunctionType
Length of the RpcResponseHeaderProtovarint
RpcResponseHeaderProtobytes
Length of the RPC responseuint32
Length of the Exeption class nameuint32
Exception class nameutf-8 string
Length of the stack traceuint32
Stack traceutf-8 string
 

 

总结

以上是生活随笔为你收集整理的Hadoop RPC protocol description--转的全部内容,希望文章能够帮你解决所遇到的问题。

如果觉得生活随笔网站内容还不错,欢迎将生活随笔推荐给好友。