[
https://issues.apache.org/jira/browse/HADOOP-12957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259000#comment-15259000
]
Xiaobing Zhou commented on HADOOP-12957:
----------------------------------------
Patch v002 used a different way to probe limit of async calls, e.g.
{code}
for (;;) {
try {
doCall(idx, param);
return;
} catch (AsyncCallLimitExceededException e) {
/**
* reached limit of async calls, fetch results of finished async calls
* to let follow-on calls go
*/
start = end;
end = idx;
waitForReturnValues(start, end);
}
}
{code}
Thank you [~szetszwo] for the comment.
> Limit the number of outstanding async calls
> -------------------------------------------
>
> Key: HADOOP-12957
> URL: https://issues.apache.org/jira/browse/HADOOP-12957
> Project: Hadoop Common
> Issue Type: Improvement
> Components: ipc
> Reporter: Xiaobing Zhou
> Assignee: Xiaobing Zhou
> Attachments: HADOOP-12957-HADOOP-12909.000.patch,
> HADOOP-12957-combo.000.patch, HADOOP-12957.001.patch, HADOOP-12957.002.patch
>
>
> In async RPC, if the callers don't read replies fast enough, the buffer
> storing replies could be used up. This is to propose limiting the number of
> outstanding async calls to eliminate the issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
