varnish load balance - HLS

[Laszlo Danielisz]

Timeout is set to 1 second for each probe

Here is a varnishlog -O 

# varnishlog -O
    0 Backend_health - backend1 Still healthy 4--X--- 3 3 5 0.000000 0.000000 HTTP/1.1 200 OK
Accept-Ranges: bytes
Server: WowzaStreamingEngine/4.1.0
Cache-Control: no-cache
Connection: close
Content-T
    0 Backend_health - backend3 Still healthy 4--X--- 3 3 5 0.000000 0.000000 HTTP/1.1 200 OK
Accept-Ranges: bytes
Server: WowzaStreamingEngine/4.1.0
Cache-Control: no-cache
Connection: close
Content-T
    0 CLI          - Rd ping
    0 CLI          - Wr 200 19 PONG 1414180168 1.0
    0 CLI          - Rd ping
    0 CLI          - Wr 200 19 PONG 1414180171 1.0
    0 CLI          - Rd ping
    0 CLI          - Wr 200 19 PONG 1414180174 1.0
    0 CLI          - Rd ping
    0 CLI          - Wr 200 19 PONG 1414180177 1.0
    0 Backend_health - backend2 Still healthy 4--X--- 3 3 5 0.000000 0.000000 HTTP/1.1 200 OK
Accept-Ranges: bytes
Server: WowzaStreamingEngine/4.1.0
Cache-Control: no-cache
Connection: close
Content-T
    0 Backend_health - backend3 Still healthy 4--X--- 3 3 5 0.000000 0.000000 HTTP/1.1 200 OK
Accept-Ranges: bytes
Server: WowzaStreamingEngine/4.1.0
Cache-Control: no-cache
Connection: close
Content-T
    0 Backend_health - backend0 Still healthy 4--X--- 3 3 5 0.000000 0.000000 HTTP/1.1 200 OK
Accept-Ranges: bytes
Server: WowzaStreamingEngine/4.1.0
Cache-Control: no-cache
Connection: close
Content-T
    0 Backend_health - backend1 Still healthy 4--X--- 3 3 5 0.000000 0.000000 HTTP/1.1 200 OK
Accept-Ranges: bytes
Server: WowzaStreamingEngine/4.1.0
Cache-Control: no-cache
Connection: close
Content-T
    0 CLI          - Rd ping
    0 CLI          - Wr 200 19 PONG 1414180180 1.0
    0 CLI          - Rd ping
    0 CLI          - Wr 200 19 PONG 1414180183 1.0
    0 CLI          - Rd ping
    0 CLI          - Wr 200 19 PONG 1414180186 1.0
    0 Backend_health - backend2 Went sick 4--X--- 2 3 5 0.000000 0.000000 HTTP/1.1 200 OK
Accept-Ranges: bytes
Server: WowzaStreamingEngine/4.1.0
Cache-Control: no-cache
Connection: close
Content-T
    0 Backend_health - backend3 Went sick 4--X--- 2 3 5 0.000000 0.000000 HTTP/1.1 200 OK
Accept-Ranges: bytes
Server: WowzaStreamingEngine/4.1.0
Cache-Control: no-cache
Connection: close
Content-T
    0 Backend_health - backend0 Went sick 4--X--- 2 3 5 0.000000 0.000000 HTTP/1.1 200 OK
Accept-Ranges: bytes
Server: WowzaStreamingEngine/4.1.0
Cache-Control: no-cache
Connection: close
Content-T
    0 Backend_health - backend1 Went sick 4--X--- 2 3 5 0.000000 0.000000 HTTP/1.1 200 OK
Accept-Ranges: bytes
Server: WowzaStreamingEngine/4.1.0
Cache-Control: no-cache
Connection: close
Content-T


On Thursday, October 23, 2014 10:25 PM, Laszlo Danielisz <laszlo.danielisz at yahoo.com> wrote:
 


I can look this up tomorrow and will let you know. 
From:"Andreas Plesner Jacobsen" <apj at mutt.dk>
Date:Thu, Oct 23, 2014 at 16:29
Subject:Re: varnish load balance - HLS


On Thu, Oct 23, 2014 at 06:30:07AM -0700, Laszlo Danielisz wrote:
> 
> I'm sending the varnishlog, I could not find anything about the request in it.

Either you have very high timeouts in varnish or you're not hitting varnish.
This looks like varnish 3, so try disabling log collation with varnishlog -O

> What is interesting is that varnish reports the backends sick after a couple
> seconds
 BUT with "HTTP 200 OK", while the .url defined in the probe is still
> up.

Did you configure a 0 second timeout for those probes?


-- 
Andreas

_______________________________________________
varnish-misc mailing list
varnish-misc at varnish-cache.org
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20141024/6ba1f3ca/attachment-0001.html>