> -----Original Message----- > From: Pid [mailto:p...@pidster.com] > > Another option is to configure mod_jk for static hostnames then use > > either /etc/hosts or an actual DNS cluster to change the mappings. > > This relies on the application in question honoring DNS TTLs (hint: > > Java doesn't by default). The good news is, it appears that > > mod_proxy_balancer at least honors /etc/hosts. > > > > This is actually my current favorite option, but it just seems like a > > grand hack, and it doesn't allow me to _ADD_ hosts to the config, only > > change them. So I'm likely to configure a large number of workers who > > will not be running most of the time, let the auto-scaling system make > > the workers work or not-work as it brings instances up and down, and > > accept the restart of Apache when I have to increase the max number of > > workers. > > > > It's not pretty, but it looks like it'll work. > > Cheap & dirty. > > 1. pre-configure each load balancer with a list of disabled workers: > > <Proxy balancer://mycluster> > BalancerMember http://tomcat01.mynet.internal:8009 > BalancerMember http://tomcat02.mynet.internal:8009 > BalancerMember http://tomcat03.mynet.internal:8009 > > # ... > BalancerMember http://tomcat99.mynet.internal:8009 status=D </Proxy> > > 2. update the hosts file on the load balancer to assign your newly > created virtual server IPs to one of the fake domain names above > > 3. enable the no-longer-a-dummy host using the /balancer-manager URLs > > > A variation on this will probably work for mod_jk, it might even work > better.
...isn't that what I just described? Or is there a part to your suggestion I missed? -Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
