Ruslan,<br>   Thanks for your response.<br>  -kvh<br><br><div class="gmail_quote">On Mon, Aug 6, 2012 at 2:08 PM, Ruslan Ermilov [via nginx] <span dir="ltr"><<a href="/user/SendEmail.jtp?type=node&node=7581133&i=0" target="_top" rel="nofollow" link="external">[hidden email]</a>></span> wrote:<br>

<blockquote style='border-left:2px solid #CCCCCC;padding:0 1em' class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">

        On Sun, Aug 05, 2012 at 10:10:39PM -0700, kvhdude wrote:

<br>> Folks,

>   Can anyone help me out?

<br>>   To clarify: I am just looking for confirmation as i add an upstream

<br>> server, will hash change for existing users (these are using XMPP sessions

> so they will suffer disruption of service).

</div>Yes, it will.  The hashing implemented by ip_hash is not consistent.

<br><br>There's limited support for preserving hash values when a server in

<br>an upstream goes down, in the form of the "down" parameter, please

see <a href="http://nginx.org/r/ip_hash" rel="nofollow" link="external" target="_blank">http://nginx.org/r/ip_hash</a> for details.

Adding consistent hashing is planned in future versions of nginx.

<br><div class="im"><div><div class='shrinkable-quote'><br>> kvhdude wrote

<br>> > 

<br>> > Hi,

<br>> > 

<br>> > I need a clarification regarding ip_hash directive :

<br>> > Would adding a new upstream server affect existing users that are bound to

<br>> > some other servers?

<br>> > I am trying to dynamically scale up the servers (using scalr) in EC2

<br>> > setting.

<br>> > 

> > I am guessing it won't, but i needed to be sure.

</div></div></div>_______________________________________________

<br>nginx mailing list

<br><a href="http://user/SendEmail.jtp?type=node&node=7581131&i=0" rel="nofollow" link="external" target="_blank">[hidden email]</a>

<br><a href="http://mailman.nginx.org/mailman/listinfo/nginx" rel="nofollow" link="external" target="_blank">http://mailman.nginx.org/mailman/listinfo/nginx</a><br>

        <br>

        <br>

        <hr color="#cccccc" noshade size="1">

        <div style="color:#444;font:12px tahoma,geneva,helvetica,arial,sans-serif"><div class="im">

                <div style="font-weight:bold">If you reply to this email, your message will be added to the discussion below:</div>

                </div><a href="http://nginx.2469901.n2.nabble.com/upstream-server-and-ip-hash-tp7580949p7581131.html" target="_blank" rel="nofollow" link="external">http://nginx.2469901.n2.nabble.com/upstream-server-and-ip-hash-tp7580949p7581131.html</a>

        </div><div class="HOEnZb"><div class="h5">

        <div style="color:#666;font:11px tahoma,geneva,helvetica,arial,sans-serif;margin-top:.4em;line-height:1.5em">

                To unsubscribe from upstream server and ip hash, <a href="" target="_blank" rel="nofollow" link="external">click here</a>.<br>

                <a href="http://nginx.2469901.n2.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml" rel="nofollow" style="font:9px serif" target="_blank" link="external">NAML</a>

        </div></div></div></blockquote></div><br>

<br/><hr align="left" width="300" />

View this message in context: <a href="http://nginx.2469901.n2.nabble.com/upstream-server-and-ip-hash-tp7580949p7581133.html">Re: upstream server and ip hash</a><br/>

Sent from the <a href="http://nginx.2469901.n2.nabble.com/">nginx mailing list archive</a> at Nabble.com.<br/>