[Varnish] #518: Default backend health right after launch

Varnish varnish-bugs at projects.linpro.no
Thu Jun 18 13:40:03 CEST 2009

#518: Default backend health right after launch
 Reporter:  rts     |        Owner:       
     Type:  defect  |       Status:  new  
 Priority:  normal  |    Milestone:       
Component:  build   |      Version:  trunk
 Severity:  normal  |   Resolution:       
 Keywords:          |  
Comment (by whocares):

 > Currently, the user experience is 503 errors instead of an abrupt
 connection refused.
 > I'm not fully convinced that's necessarily bad, or at least any worse
 than the alternatives.

 Actually in my case sending out 503s *is* worse than sending "Connection
 refused". That's simply because most of our users accept "Connection
 Refused" as the server being down for some reason or other whereas 503s
 are (for reasons unknown to me) associated with a faulty application. For
 the latter in turn our internal development department is blamed by
 management and that's the *real* problem.

 So basically I'm infavour of the "default healthy" state but as I already
 wrote in the other thread: For me it'd be enough to add an command line
 switch to varnish that activates the "default healthy" behaviour.


Ticket URL: <http://varnish.projects.linpro.no/ticket/518#comment:3>
Varnish <http://varnish.projects.linpro.no/>
The Varnish HTTP Accelerator

More information about the varnish-bugs mailing list