On Oct 16, 2007, at 5:30 PM, Chris Chen wrote:
> Considering that Resin now has a watchdog process that monitors the
> servers, is it possible to simply have the watchdog monitor and start
> multiple resin servers?
Yep. It does that now.
When you start a second Resin, the resin.jar process contacts the
watchdog and asks it to run the new Resin.
> Here's what I'm thinking why this is good.
> 1) One startup script to startup resin. No need to create multiple
> startup scripts that each runs a separate resin instance.
> 2) One resin watchdog process.
> 3) One resin configuration file (which already contains all the
> configurations anyways). I can create multiple resin cluster
> segments that launches hosts all the same apps and services within
> each cluster. I can also have multiple hosts specified that launches
> only the services/apps specific to that host.
I'd think this would be the most important one. That way you know
everything is in one config file.
Also, it lets Resin's admin display information for everything
configured in that resin.conf. The 3.1.3 resin-admin has an improved
cluster display that will show an overview of every server in the
> I'm not sure if this is possible at the moment or not. But it'd be
> great. Resin's watchdog can actually look at different clustered
> hosts, check if each the host it's running on matches a host inside
> each cluster, and then launch a separate resin server for each
> This way, it's like running one MySQL service manager that can start
> up multiple instances of mysql server (different versions, different
> databases, etc). MySQL also only uses one config file for all the
> resin-interest mailing list
resin-interest mailing list