Mod_proxy_balancer question

Rails
#1

Here’s the problem, I want to start running more mongrels on a 2nd
server, but I want it so that any file uploads still go to the 1st
server.

Anyone know how I can do this?

#2

Hi David,

Here’s the problem, I want to start running more mongrels on a 2nd
server, but I want it so that any file uploads still go to the 1st
server.

You’ll need some sort of Layer 7 rules engine to configure that, which
mod_proxy_balancer doesn’t have. Alternatively you could look into using
some sort of shared storage such as NFS, Samba or GFS.

–
Roderick van Domburg
http://www.nedforce.nl

#3

On Aug 14, 8:53 pm, Roderick van Domburg <rails-mailing-l…@andreas-
s.net> wrote:

Hi David,

Here’s the problem, I want to start running more mongrels on a 2nd
server, but I want it so that any file uploads still go to the 1st
server.

You’ll need some sort of Layer 7 rules engine to configure that, which
mod_proxy_balancer doesn’t have. Alternatively you could look into using
some sort of shared storage such as NFS, Samba or GFS.

You can definitely change which mongrels you balance to based on the
url. I wouldn’t be surprised if you could rewrite based on the content-
type header (and all file uploads will have the multipart etc content
type.

Fred

#4

You can definitely change which mongrels you balance to based on the
url. I wouldn’t be surprised if you could rewrite based on the content-
type header (and all file uploads will have the multipart etc content
type.

Fred

Yeah the URL would be enough, there’s only one action that handles file
uploads. Can you give me any pointers on this, what would I need to
write in the conf file?

#5

On Aug 14, 9:42 pm, David F. <rails-mailing-l…@andreas-
s.net> wrote:

You can definitely change which mongrels you balance to based on the
url. I wouldn’t be surprised if you could rewrite based on the content-
type header (and all file uploads will have the multipart etc content
type.

Fred

Yeah the URL would be enough, there’s only one action that handles file
uploads. Can you give me any pointers on this, what would I need to
write in the conf file?

our vhost has got something like

RewriteRule ^/admin/.$ balancer://admin_cluster%{REQUEST_URI}
[P,QSA,L]
RewriteRule ^/report/.$ balancer://admin_cluster%{REQUEST_URI}
[P,QSA,L]

All other URLs should be served by the texpert cluster

RewriteRule ^/.*$ balancer://main_cluster%{REQUEST_URI} [P,QSA,L]

urls starting with /admin and /report go the the admin_cluster, and
the others to the main_cluster.

Fred

#6

our vhost has got something like

RewriteRule ^/admin/.$ balancer://admin_cluster%{REQUEST_URI}
[P,QSA,L]
RewriteRule ^/report/.$ balancer://admin_cluster%{REQUEST_URI}
[P,QSA,L]

All other URLs should be served by the texpert cluster

RewriteRule ^/.*$ balancer://main_cluster%{REQUEST_URI} [P,QSA,L]

urls starting with /admin and /report go the the admin_cluster, and
the others to the main_cluster.

Fred

That looks perfect, I’ll give it a go.

Thanks Fred!

#7

Hi David,

You can definitely change which mongrels you balance to based on the
url. I wouldn’t be surprised if you could rewrite based on the content-
type header (and all file uploads will have the multipart etc content
type.

Yeah the URL would be enough, there’s only one action that handles file
uploads. Can you give me any pointers on this, what would I need to
write in the conf file?

Frederick is right – thanks for making me read up on my mod_proxy
knowledge! I was under the assumption that this required more expensive
hardware balancing, so this is cool.

Check out the ProxyPass directives at the mod_proxy documentation at
http://httpd.apache.org/docs/2.2/mod/mod_proxy.html. It’s got ample
examples.

–
Roderick van Domburg
http://www.nedforce.nl