Hmm, if you've background fill enabled and tuned correctly for RWW, the client
abort should not impact the Origin fetch.
https://docs.trafficserver.apache.org/en/7.1.x/admin-guide/configuration/cache-basics.en.html#admin-config-read-while-writer
However, if the Origin is completely broken or if background fill isn't
enabled, then all the waiting client requests will result in being proxied to
the Origin (treated as a cache miss).
Is that what you are noticing?
On Monday, June 22, 2020, 04:23:16 AM PDT, ezko
<erez.ko...@harmonicinc.com> wrote:
Hi Sudheer ,
we ran some more tests and actually found 2 leaks that were for a ~100 Kb
segment.
it's a strange scenario. for these segments we never saw a crc equaling
Cache Miss , instead the first crc was ERR_CLIENT_READ_ERROR.
So it seems like the first client to get the write lock aborted due to
network problems.
What is the expected behavior in this case ?
>From the logs it seems that afterwards all clients were redirected to the
origin (not proxied)
For each client we saw 2 log entries , a 303 with ERR_CONNECT_FAIL and a 303
with TCP_MISS_REDIRECT
Thanks,
Erez
--
Sent from: http://apache-traffic-server.24303.n7.nabble.com/
