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

Posted to dev@thrift.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2015/07/31 00:21:04 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14648400#comment-14648400 ] 

Hudson commented on THRIFT-3279:
--------------------------------

SUCCESS: Integrated in Thrift #1634 (See [https://builds.apache.org/job/Thrift/1634/])
THRIFT-3279 Fix a bug in retry_max_delay (roger: rev 4ed2b855e9dec14afe859330e4f620d026d903e3)
* lib/nodejs/lib/thrift/connection.js


> 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
>            Assignee: Roger Meier
>         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)