[Varnish] #644: Deadlock in 2.0.x under high load.

[Varnish]

#644: Deadlock in 2.0.x under high load.
----------------------+-----------------------------------------------------
 Reporter:  kmcfate   |        Owner:  kristian
     Type:  defect    |       Status:  reopened
 Priority:  normal    |    Milestone:          
Component:  varnishd  |      Version:  2.0     
 Severity:  normal    |   Resolution:          
 Keywords:  deadlock  |  
----------------------+-----------------------------------------------------
Changes (by kristian):

  * status:  closed => reopened
  * resolution:  fixed =>

Comment:

 Reopening this based on reports that this switches the deadlock into a
 spin. While better, obviously not optimal.

 This probably means there's some data "stuck" in a pipe that we're not
 picking up. This would also explain why the buffer space fills up. I've
 got a core dump to investigate and will follow it up.

-- 
Ticket URL: <http://varnish-cache.org/ticket/644#comment:7>
Varnish <http://varnish.projects.linpro.no/>
The Varnish HTTP Accelerator