What I was actually referring to is that the nginx configuration can specify the total number of connections to the entire set of upstream app servers (worker_processes * worker_connections). If this is the case and we scale up the app servers at any point, then the total number of connections from nginx will be divided by the new number of app servers - hence, less connections per app server. This is probably not what we want when we are trying to increase the throughput of the overall application. If instead, as the app servers scale up, we could also send an snmp trap to the nginx tier of servers to make sure that nginx servers adjust the number of connections to make sure that the number of connections per app server is above a specified minimum.
Does this make sense? Akshay On Tue, Mar 9, 2010 at 1:21 PM, Nickolas Toursky <[email protected]> wrote: > Ken, > > There is a template file /usr/local/aws/templates/app-servers.tmpl > which is used to build nginx upstreams configuration. Just remove > "ip_hash" from there. > > Regards, > Nick > > On 9 March 2010 16:41, kenhawkins <[email protected]> wrote: > > Is there a way to control that setting from within the scalr env? ala > > not write ip_hash to the app-servers.include? I didn't see anything... > > > > thanks, > > Ken; > > > > On Mar 9, 7:34 am, Nickolas Toursky <[email protected]> wrote: > >> Akshay, > >> > >> nginx is reloaded each time upstream configuration is changed. > >> Client IP addresses are hashed to make all requests from the same > >> client to go to the same upstream (for session persistence). > >> With IP hashing turned off each app server will get the same amount of > >> connections as others. Is this what you are interested in? > >> > >> Regards, > >> Nick > >> > >> On 21 February 2010 21:41, Akshay Rao <[email protected]> wrote: > >> > >> > When scalr scales up and down either the app servers or web servers, > there > >> > will be a discrepancy between the number of connections that the app > server > >> > takes in and the number of nginx connections per app server. Is there > a way > >> > to modify the number of nginx connections and reload nginx as the > app/web > >> > server scale? > >> > >> > If not, could this be a new feature? For high performance sites, I > would > >> > imagine that this would be a great feature. > >> > >> > Regards, > >> > >> > Akshay > >> > >> > -- > >> > 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]<scalr-discuss%[email protected]> > . > >> > For more options, visit this group at > >> >http://groups.google.com/group/scalr-discuss?hl=en. > >> > >> > > > > -- > > 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]<scalr-discuss%[email protected]> > . > > For more options, visit this group at > http://groups.google.com/group/scalr-discuss?hl=en. > > > > > > -- > 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]<scalr-discuss%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/scalr-discuss?hl=en. > > -- 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.
