MogileFS module for nginx - sanity check + anyone interested?

mike mike503 at gmail.com
Thu May 1 15:35:43 UTC 2008


On 5/1/08, Timo Ewalds <timo at tzc.com> wrote:
> I agree, this is rather domain specific, and therefore not too useful. I
> propose instead to add a general purpose reproxy module to nginx, which
> would keep the domain specific url rewriting in your http/fcgi backend, but
> let nginx still do the webserving. Perlbal has this feature, and but I don't
> think either lighttpd or nginx do. To be fair, lighttpd 1.5 sort of has it,
> though it needs to know about all the mogstore daemons ahead of time. The
> way perlbal (or squid) does it you just pass back a full url in a header,
> and it just does the request, making it much more flexible. Since
> lighttpd/nginx don't do this, our Ruby code is doing both the url
> translation and the request to the mogstored, which is much less efficient
> than Ruby just did the url translation and let lighttpd/nginx do the
> mogstore proxying.

The rationale for this is hoping to skip having to go into
PHP/Perl/application level code.

I believe nginx can already do it today, if you involve a PHP level
script to determine the storage node(s) to try, and then tell nginx to
grab it from there...

I found a site[1] in Japanese that from what I can tell has determined
how to do it. But to be able to skip needing any PHP level code would
be great; it would allow the webserver to use MogileFS as a pseudo
filesystem for a large majority of most websites' files (well, those
that have user generated data) - or I guess *any* assets.

1. http://d.hatena.ne.jp/perezvon/20080418/1208531594


More information about the mogilefs mailing list