[Varnish] #537: Sticky director

Varnish varnish-bugs at projects.linpro.no
Tue Aug 4 20:26:02 CEST 2009

#537: Sticky director
 Reporter:  rts       |        Owner:  phk              
     Type:  defect    |       Status:  new              
 Priority:  low       |    Milestone:  After Varnish 2.1
Component:  varnishd  |      Version:  trunk            
 Severity:  normal    |   Resolution:                   
 Keywords:            |  
Comment (by kb):

 Is your goal a distinct "primary/failover" setup (use server B only if A
 failed, and revert back to A when it becomes healthy again) or generalized

 I think you could implement both in VCL, so the question that comes to my
 mind is whether its use would be widespread enough to justify added
 director complexity.

 I think primary/failover might be worthy, but adding features to the
 "director" could be a slippery slope -- there are literally hundreds of
 major features that could be added that exist in, say, LVS or Netscalers
 or BigIPs.

 The other feature I'd like to see is a least-connections director.  Past
 that, I'm not sure I wouldn't implement more complex
 balancing/persistence/etc on dedicated up-stream systems.

 Just my US$0.02,

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

More information about the varnish-bugs mailing list