Project

General

Profile

Feature #3270

Add maximum back-off parameter for "limit"?

Added by Peter Shanahan over 8 years ago. Updated over 3 years ago.

Status:
Accepted
Priority:
Low
Assignee:
-
Target version:
-
Start date:
Due date:
09/30/2013
% Done:

0%

Estimated time:
0.00 h
Duration:

Description

The "limit" parameter causes an exponential back-off of messages, apparently with no upper limit on the interval between allowed messages. It would be nice if there could be an upper limit to this interval, so for example,

limit : 5
max_backoff : 100

would result in

1, 2, 3, 4, 5, 10, 15, 25, 45, 85, 185, 285, 385, ....
(By the way, I'm taking the 1st 10 numbers from the documentation. Wouldn't it actually be
1, 2, 3, 4, 5, 10, 20, 40, ....?)

Budget note: we couldn't pay for this on NOvA project. I assume MF support is already from non-project funds?

Schedule note: Please take due date with a grain of salt - not at all urgent.

Related issues

Related to art - Bug #3571: Message logger configurationAccepted09/30/2013

History

#1 Updated by Christopher Green over 7 years ago

  • Due date changed from 02/28/2013 to 09/30/2013
  • Status changed from New to Accepted
  • Assignee deleted (Qiming Lu)
  • Target version set to 1.09.00
  • Start date deleted (01/12/2013)
  • Estimated time set to 0.00 h

This should be implemented as part of the solution for issue #3571, and should not take any time over the estimate for that issue.

#2 Updated by Christopher Green about 7 years ago

  • Target version changed from 1.09.00 to 521

#3 Updated by Kyle Knoepfel over 3 years ago

  • Target version deleted (521)

Also available in: Atom PDF