[
https://issues.apache.org/jira/browse/HADOOP-16192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16795122#comment-16795122
]
Hudson commented on HADOOP-16192:
---------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #16232 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/16232/])
HADOOP-16192. Fix CallQueue backoff bugs: perform backoff when add() is
(xkrogen: rev 8c95cb9d6bef369fef6a8364f0c0764eba90e44a)
* (edit)
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/ipc/TestCallQueueManager.java
* (edit)
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/ipc/Server.java
* (edit)
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/ipc/TestRPC.java
* (edit)
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/ipc/CallQueueManager.java
> 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
> Attachments: 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]
