[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Error running context

From: Bert Huijben <bert_at_qqmail.nl>
Date: Sun, 2 Dec 2012 20:54:49 +0000

ra_serf is capable of retrying some failed requests (and even on picking up
from where the failed request stopped) for our xml reports.

I think gstein added this feature during 1.7 development.

Bert

 *From:* Lieven Govaerts <svnlgo_at_mobsol.be>
*Sent:* December 2, 2012 9:26 PM
*To:* Justin Erenkrantz <justin_at_erenkrantz.com>
*CC:* Subversion Development <dev_at_subversion.apache.org>
*Subject:* Re: Error running context

Hi,

On Sun, Dec 2, 2012 at 3:18 PM, Justin Erenkrantz <justin_at_erenkrantz.com>
wrote:
> On Sun, Dec 2, 2012 at 9:05 AM, Lieven Govaerts <svnlgo_at_mobsol.be> wrote:
>>
>> Attached the patch. ( I get paid per mail I send to this list in case
>> no one noticed. ;) )
>
>
> The patch looks right to me - the short-circuit to do the simple window
can
> clearly be called for any window regardless of offset. Perhaps we can add
> this testcase to the regression tests as well?
>
> As for the looping, didn't we put in logic to stop retrying after a number
> of request failures? That's probably a reasonable thing to do...I
> definitely think a very nice feature of serf is that it *will* retry
(which
> is helpful in flaky network situations), but it needs to stop at a certain
> point. =) -- justin

Serf is resending requests that were waiting on the pipeline to be
handled by the server, but when a read error is received it will not
resend the request.
Maybe ra_serf is doing that in some situations, but I don't think so either.

The issue here is that serf trunk was ignoring a read error on the
connection with an outstanding request, as a side effect if r1695.
That has been fixed in r1696.

Lieven
Received on 2012-12-02 21:55:22 CET

This is an archived mail posted to the Subversion Dev mailing list.