[Varnish] #1057: Varnish 3.0.2-streaming stops forwarding requests

Varnish varnish-bugs at varnish-cache.org
Thu Nov 10 17:52:24 CET 2011

#1057: Varnish 3.0.2-streaming stops forwarding requests
 Reporter:  hidi      |       Owner:  martin   
     Type:  defect    |      Status:  new      
 Priority:  normal    |   Milestone:           
Component:  varnishd  |     Version:  3.0.2    
 Severity:  major     |    Keywords:  streaming

Comment(by hidi):

 Dear Marin,

 Thanks, it solves the problem, so the client receive the answer now.
 However it works with the first connection fine, after a few connections
 to a (slow) stream source. The second or third source will receive the
 data very slowly with a great timeout. Probably this is because of
 something chunk buffer, but it's still anoying for some ajax applications
 for example. As many users use SEF URLs we cannot tell wether we should
 switch to pipe mode or serve the query as usual at vlc_recv time, but we
 can tell it at vcl_fetch.

 I've tested that 3.0.2 (single connection) works great if I switch on

 My personal idea and question is that is it possible to switch to pipe or
 stream mode and UNLOCK! the object what we will never cache at vcl_fetch

 Second "hack" is that to simply ignore somehow the lock. We have some
 pages using ajax or slow stream sources they will mess up without a

 I think if we could unlock the unnecesarry object lock it would solve this
 great streaming problem without other fetching threads!

Ticket URL: <https://www.varnish-cache.org/trac/ticket/1057#comment:5>
Varnish <https://varnish-cache.org/>
The Varnish HTTP Accelerator

More information about the varnish-bugs mailing list