On 17.04.2009 21:44, David Fisher wrote: > Rainer - > > Wouldn't this type of dynamics occur if your workers were in a cloud? Or > if you needed a lot more very quickly for peak processing?
Yes, but then you should extend your dynamics to your other configurations as well. In fact there are tendencies now with mod_cluster and mod_heartbeat to detect farm topology automatically. But with mod_jk we are not there yet. So you need to take care of the configuration with external mechanisms. > Am I correct to think that if someone is being so "dynamic" with their > worker's DNS configuration then they should automate using the status > worker to handle configuration after initial startup of mod_jk? > > http://tomcat.apache.org/connectors-doc/reference/status.html > > Unfortunately, I don't see a way to add or remove a worker? I think that > this type of dynamic configuration would be very helpful in managing a > cloud of tomcat workers. The status worker does not allow to persist the changes. This will come soon :) > I would be pretty cool to be able to put Tomcat Workers into service > merely by starting up a VM that uses DHCP to get its IP by name. The VM > could then know to register itself with a mod_jk status worker. Wouldn't > this make a Tomcat Cloud super easy to manage? It could even be > geographically diverse and migratory. As noted above there are brand new modules for dynamic farm topology detection. I exoect a lot of improvement in this area in the next 1-2 years. Regards, Rainer > On Apr 17, 2009, at 10:16 AM, Rainer Jung wrote: > >> On 17.04.2009 18:02, André Warnier wrote: >>> To my knowledge, the only case where the DNS would fail to provide an IP >>> address of a correctly-written FQDN name, is if you have some >>> configuration where your hosts register themselves under some variable >>> IP address when they startup. But that would be a strange setup for >>> servers, no ? >> >> Maybe some combination with DHCP? But I still don't like the concept of >> this type of dynamics. >> >> Regards, >> >> Rainer --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
