You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Erik Krogen (JIRA)" <ji...@apache.org> on 2019/03/14 17:12:00 UTC

[jira] [Updated] (HADOOP-16192) CallQueue backoff bug fixes: doesn't perform backoff when add() is used, and doesn't update backoff when refreshed

     [ https://issues.apache.org/jira/browse/HADOOP-16192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Erik Krogen updated HADOOP-16192:
---------------------------------
    Summary: CallQueue backoff bug fixes: doesn't perform backoff when add() is used, and doesn't update backoff when refreshed  (was: CallQueue doesn't perform backoff when add() is used)

> 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
>
> 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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org