yea...but by IP to where? It needs to make sure that it sends a request to a valid server.
If IP x goes to server 1 but server 1 is now dead...how often is the app server list updated to reflect that server 1 does not exist. I guess it is supposed to be dns stuff that removes it from the app servers list? By the way...if this is the way it is handled then the only way nginx will have a server removed from the load balancing is by dns? if there is an application that gets stuck (server remains up) it will keep redirecting requests to it? no way to define some health check? 2009/3/23 Alex Kovalyov <[email protected]> > > Disregard previous reply. > no cookies. > It sticks you by IP addy. > > On 23 мар, 13:05, Alex Kovalyov <[email protected]> wrote: > > Per FAQ (scalr.net/faq.php), LB(nginx) uses cookies to stick client to > > a particular app instance. > > > > Check logs. > > > > On 22 мар, 05:35, Nathan Palmer <[email protected]> wrote: > > > > > It seems like we have a problem where users of my site are getting > > > stuck sending their traffic to a server that is possibly not in use > > > anymore. They get the SCALR error page, but if they clear their cache/ > > > cookies and try again it goes just fine. > > > > > Is it storing something in a cookie that keeps them going to the > > > server that doesn't exist? > > > > > Nathan > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
