[
https://issues.apache.org/jira/browse/HADOOP-9717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13712370#comment-13712370
]
Tsz Wo (Nicholas), SZE commented on HADOOP-9717:
------------------------------------------------
> protobuf uses varint to encode int32/sint32 etc
> (https://developers.google.com/protocol-buffers/docs/encoding). Thus using
> byte for retry count and keep it within the range 0~0xFE should be able to
> decrease the overhead ...
It is rare to have retry count > 100. Given that protobuf is already using
varint, it is unnecessary to restrict retry count to be a byte. So I suggest
simply using sint32 in protobuf and int in Java.
> Add retry flag/retry attempt count to the RPC requests
> ------------------------------------------------------
>
> Key: HADOOP-9717
> URL: https://issues.apache.org/jira/browse/HADOOP-9717
> Project: Hadoop Common
> Issue Type: Improvement
> Components: ipc
> Affects Versions: 3.0.0
> Reporter: Suresh Srinivas
> Assignee: Jing Zhao
> Attachments: HADOOP-9717.000.patch, HADOOP-9717.001.patch,
> HADOOP-9717.002.patch, HADOOP-9717.003.patch
>
>
> RetryCache lookup on server side implementation can be optimized if Rpc
> request indicates if the request is being retried. This jira proposes adding
> an optional field to Rpc request that indicates if request is being retried.
--
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
