mogilefs module 1.0.2

Valery Kholodkov valery+nginxen at
Mon Jul 27 21:48:10 MSD 2009

Hello Michael!

Michael Shadle wrote:
> Ah, so the module does all the work, instead of the client contacting
> the tracker, and the tracker using the nginx-based mogstored; this
> actually takes the file itself and pushes it into the mogilefs system
> for you?

Yes, this is what it was written for.

> I suppose that's a pretty cool feature then. Anything to keep
> configuration light and usability the easiest.
> On Mon, Jul 27, 2009 at 2:48 AM, Valery
> Kholodkov<valery+nginxen at> wrote:
>> This is to use nginx as a frontend to MogileFS and hide interaction with the tracker while store files.
>> ----- Michael Shadle <mike503 at> wrote:
>>> Just for discussion sake why is that? I actually have the same
>>> instance of nginx with two separate http{} blocks. One for mogstored
>>> and one for normal web serving. It might even be possible to have it
>>> under the same http block. I never looked into it that much.
>>> I guess explaining the pros and cons of doing it that way vs. Using
>>> the module would be good info to know.
>>> Sent from my iPhone
>>> On Jul 25, 2009, at 2:20 PM, Valery Kholodkov <valery+nginxen at
>>>  > wrote:
>>>> Yes, but making a mogstored node out of it is a bad idea.
>>>> Michael Shadle wrote:
>>>>> So this means this module now handles the DAV requests as well, so it
>>>>> can be a mogstored node?
>>>>> nginx technically already supported that :) However this could be
>>>>> more
>>>>> efficient, etc. I'm wondering if I am understanding this properly.
>>>>> On Sat, Jul 25, 2009 at 10:22 AM, Valery
>>>>> Kholodkov<valery+nginxen at> wrote:
>>>>>> Changes in version 1.0.2 (July 25 2009):
>>>>>> * Added feature: directive mogilefs_methods and support for PUT
>>>>>> and DELETE
>>>>>> methods
>>>>>> * Added feature: dynamic evaluation of tracker name
>>>>>> * Added feature: ability to pass noverify parameter to tracker
>>>>>> The first 2 features were commissioned by GG Network SA (
>>>>>> ).
>>>>>> These features allow write access to MogileFS using nginx, as well
>>>>>> as
>>>>>> locating of tracker dynamically. The Gadu-Gadu developers were
>>>>>> very kind to
>>>>>> test these features. Hopefully there are no major issues.
>>>>>> The noverify parameter instructs MogileFS tracker to avoid
>>>>>> querying the
>>>>>> database for location of files if possible and use cached results,
>>>>>> thus
>>>>>> eliminating some of the database server load.
>>>>>> The details on the following page:
>>>>>> Feel free to contact me if you have problems with this!

Best regards,
Valery Kholodkov

More information about the nginx mailing list