日韩av黄I国产麻豆传媒I国产91av视频在线观看I日韩一区二区三区在线看I美女国产在线I麻豆视频国产在线观看I成人黄色短片

歡迎訪問 生活随笔!

生活随笔

當前位置: 首頁 >

Hadoop RPC protocol description--转

發布時間:2025/4/5 67 豆豆
生活随笔 收集整理的這篇文章主要介紹了 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 beSUCCESS,?ERROR?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--转的全部內容,希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網站內容還不錯,歡迎將生活随笔推薦給好友。