<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-AU link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>How does varnish handle request to multiple backend when the vcl “restart” command is run.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Does it use the same backend as the initial request or does it use another backend in accordance to the configured director.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>i.e.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>two backends b1 and b2, restart command is in vcl_error<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>request for object from b1 fails, vcl_error runs and the restart command is executed, on the next retry what backend will varnish use, b1 again or what will it act in accordance with the director (if the director was round robin would it use b2)?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I know you can explicitly script this in the vcl like in the example provided at <a href="http://northernmost.org/blog/some-trickery-or-resilience-with-varnish/">http://northernmost.org/blog/some-trickery-or-resilience-with-varnish/</a> but I currently have our backends using the round robin director and I don’t want to explicitly configure specific backends in a preference order.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Regards Glen<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div>
<TABLE border=0>
<TBODY>
<TR>
<TD><A title=""
href="http://www.fire.tas.gov.au/Show?pageId=colDayLightSavings"><IMG
border=0 hspace=0 alt=""
src="cid:tasfire_wakeup_small7eb7.jpg"></A></TD></TR>
<TR>
<TD><SPAN style="FONT-FAMILY: Webdings; COLOR: green; FONT-SIZE: 24pt">P
</SPAN><SPAN
style="FONT-STYLE: italic; FONT-FAMILY: Arial; COLOR: silver; FONT-SIZE: 7.5pt"><FONT
color=#008000>Do you need to print this? Consider the environment, prevent
paper waste.</FONT> </SPAN></TD></TR>
<TR>
<TD><SPAN
style="FONT-FAMILY: Arial; COLOR: gray; FONT-SIZE: 7.5pt">CONFIDENTIALITY
NOTICE AND DISCLAIMER<BR></SPAN><SPAN
style="FONT-FAMILY: Arial; COLOR: gray; FONT-SIZE: 7.5pt">The information
in this transmission may be confidential and/or protected by legal
professional privilege, and is intended only for the person or persons to
whom it is addressed. If you are not such a person, you are warned that
any disclosure, copying or dissemination of the information is
unauthorised. If you have received the transmission in error, please
immediately contact this office by telephone, fax or email, to inform us
of the error and to enable arrangements to be made for the destruction of
the transmission, or its return at our cost. No liability is accepted for
any unauthorised use of the information contained in this transmission.
</SPAN></TD></TR></TBODY></TABLE><br></body></html>