[
https://issues.apache.org/jira/browse/HADOOP-16192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Krogen updated HADOOP-16192:
---------------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 3.1.3
3.2.1
3.3.0
3.0.4
2.10.0
Status: Resolved (was: Patch Available)
Thanks for the review [~vagarychen]. I just committed this to trunk,
branch-3.2, branch-3.1, branch-3.0, and branch-2. There were some very minor
import conflicts in the 3.x series, and I had to change the Mockito call in
{{TestRPC}} slightly for branch-2. I've attached the updated branch-2 patch for
completeness.
> CallQueue backoff bug fixes: doesn't perform backoff when add() is used, and
> doesn't update backoff when refreshed
> ------------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-16192
> URL: https://issues.apache.org/jira/browse/HADOOP-16192
> Project: Hadoop Common
> Issue Type: Bug
> Components: ipc
> Reporter: Erik Krogen
> Assignee: Erik Krogen
> Priority: Major
> Fix For: 2.10.0, 3.0.4, 3.3.0, 3.2.1, 3.1.3
>
> Attachments: HADOOP-16192-branch-2.001.patch, HADOOP-16192.000.patch,
> HADOOP-16192.001.patch
>
>
> The {{CallQueueManager}} has a mechanism to enforce backoff when various
> criteria are met, as defined by the implementation of {{RpcScheduler}} used.
> However, it currently only checks for these backoff criteria when {{put()}}
> is used; {{add()}} calls are passed directly to the underlying call queue. It
> should check the backoff criteria for either call.
> Also, when {{refreshCallQueue()}} is called, the backoff configuration is not
> refreshed. This should be updated as well.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
