Hi all, I?m new to the list. I''ve working with mongrel for the last week and have some quetion about mongrel cluster: Is this (being executed from the application folder): # mongrel_rails start -d -p 3001 -e production # mongrel_rails start -d -p 3002 -e production # mongrel_rails start -d -p 3003 -e production the same as: # mongrel_rails cluster::configure -e production -p 3001 -N 3 -c /var/www/apps/testapp # mongrel_rails cluster::start Im not familiar with clusters, and since the load balance is being done by the Apache proxy balancer, I wonder what is the difference of executing that set of commands and the cluster::start. thanks to all, Emho
Yes, I think this is the same, but it''s easier to handle this with mongrel_cluster. Am 16.08.2006 um 06:06 schrieb Emho Verger:> Hi all, > > I?m new to the list. I''ve working with mongrel for the last week and > have some quetion about mongrel cluster: > > Is this (being executed from the application folder): > # mongrel_rails start -d -p 3001 -e production > # mongrel_rails start -d -p 3002 -e production > # mongrel_rails start -d -p 3003 -e production > > the same as: > > # mongrel_rails cluster::configure -e production -p 3001 -N 3 -c > /var/www/apps/testapp > # mongrel_rails cluster::start > > Im not familiar with clusters, and since the load balance is being > done by the Apache proxy balancer, I wonder what is the difference of > executing that set of commands and the cluster::start. > > thanks to all, > > Emho > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users
On Aug 16, 2006, at 1:51 PM, Christof Dorner wrote:> Yes, I think this is the same, but it''s easier to handle this with > mongrel_cluster. > > Am 16.08.2006 um 06:06 schrieb Emho Verger: > >> Hi all, >> >> I?m new to the list. I''ve working with mongrel for the last week and >> have some quetion about mongrel cluster: >> >> Is this (being executed from the application folder): >> # mongrel_rails start -d -p 3001 -e production >> # mongrel_rails start -d -p 3002 -e production >> # mongrel_rails start -d -p 3003 -e production >> >> the same as: >> >> # mongrel_rails cluster::configure -e production -p 3001 -N 3 -c >> /var/www/apps/testapp >> # mongrel_rails cluster::startI run each port separately, close to as you have described. I do it this way so I can run each as a daemontools service. I then have a separate daemontools service script that periodically checks each mongrel for functionality and terms/kills it if needed. Its a nice setup and allows me to not worry about anything being down for more than a minute or so. Probably overkill for general needs though.
Hi, I''d just like to share a weird problem and solution that was slowing down the browsing of the company website ... I had declared something like this (where www1.thewebname.com and www2.thewebname.com were accessible, and the IP was declared in the public DNS''s): <Proxy balancer balancer://testappcluster> BalancerMember http://www1.thewebname.com:8000 BalancerMember http://www1.thewebname.com:8001 BalancerMember http://www1.thewebname.com:8002 BalancerMember http://www2.thewebname.com:8000 BalancerMember http://www2.thewebname.com:8001 BalancerMember http://www2.thewebname.com:8002 </Proxy> However, things were very very very slow ... Then, I decided to try out changing the names for the IP''s themselves ... and things fly now ... fast as I was expecting with mongrel :) It took me sometime to realice of that and I still think it is kind of weird (it was unacceptable slow before) hope it helps someone, regards, Emho