On 22/12/2013 23:06, Marek Vavruša wrote:
Hi Marek,
To start the ball rolling, the attached patch tweaks
the settings to
double the previous interval plus jitter (30s).
I think it is a good compromise that allows relatively fast few tries
(about 3 in a few subsequent minutes) and spins
into hours in about 7 tries. Interval cap is set at the 24 hours, it
seems reasonable as the zone can be always refreshed using knotc. The
cut-off could be a bit more aggressive probably, that's the open
question.
I've had this backoff patch running for a couple of days now. If I look
at all the failing zones now, their retry period has settled at one of 2
values:
17h23m57s
17h23m58s
This means that the algorithm you've programmed ends up with this
maximum, instead of 24h. It's not a problem for me. 17h is a good enough
retry period. I just wanted Knot to stop trying to refresh these zones
aggressively, and your patch has achieved it.
However, I thought I'd provide this feedback, so that if you wish to
refine the algorithm a bit more, you have some numbers to work with.
Regards,
Anand