You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@thrift.apache.org by "Itay Duvdevani (JIRA)" <ji...@apache.org> on 2015/07/30 08:04:05 UTC

[jira] [Updated] (THRIFT-3279) Fix a bug in retry_max_delay (NodeJS)

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

Itay Duvdevani updated THRIFT-3279:
-----------------------------------
    Attachment: 0001-Fix-a-bug-in-retry_max_delay.patch

> Fix a bug in retry_max_delay (NodeJS)
> -------------------------------------
>
>                 Key: THRIFT-3279
>                 URL: https://issues.apache.org/jira/browse/THRIFT-3279
>             Project: Thrift
>          Issue Type: Bug
>          Components: Node.js - Library
>            Reporter: Itay Duvdevani
>         Attachments: 0001-Fix-a-bug-in-retry_max_delay.patch
>
>
> The current max delay is unstable - when retry_delay == retry_max_delay the second branch is taken, and retry_delay is set to retry_max_delay * retry_backoff, which is larger than retry_max_delay.
> This causes an oscillation between retry_max_delay and retry_max_delay * retry_backoff.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)