mogilefs module 1.0.2

[Valery Kholodkov]

----- Michael Shadle <mike503 at gmail.com> wrote:
> 
> 
> Sent from my iPhone
> 
> On Jul 27, 2009, at 11:14 PM, Valery Kholodkov <valery+nginxen at grid.net.ru 
>  > wrote:
> 
> > Michael Shadle wrote:
> >> This doesn't put the file on the server you're communicating with  
> >> right?
> >
> > Technically, it uses server you are communicating with as a temporary
> > storage and then creates a single replica on the first node provided  
> > by
> > tracker using PUT request.
> 
> I'm not sure if this is something you have to handle or the mogilefs  
> infrastructure does, but if you have defined multiple replicas for a  
> specific domain does this work like it should (I would assume that it  
> would return multiple nodes then)? Is it your modules responsibility  
> or does the tracker and it's processes handle distributing the files  
> amongst the other replicas?

No, at the moment it makes only one replica, but I plan to implement replication at desired minimal number of nodes simultaneously.

> 
> 
> >
> >> It still uses the tracker to determine the proper node to store the  
> >> file
> >> on right?
> >
> > Right.
> >
> >>
> >> Sent from my iPhone
> >>
> >> On Jul 27, 2009, at 10:51 PM, Valery Kholodkov
> >> <valery+nginxen at grid.net.ru> wrote:
> >>
> >>> Daniel wrote:
> >>>> Hi Valery,
> >>>> I just installed the module and recompiled nginx, set the config  
> >>>> file
> >>>> as in the example from your site.  Now i can download the files  
> >>>> from
> >>>> reverse proxy directly.  Very Cool.  Thanks a lot.
> >>>> Can you give us examples of the config to push files into the
> >>>> mogilefs storage?.
> >>>
> >>> location /upload/ {
> >>> mogilefs_tracker tracker;
> >>> mogilefs_domain domain;
> >>> mogilefs_methods PUT;
> >>> mogilefs_pass {
> >>>   proxy_pass $mogilefs_path;
> >>> }
> >>> }
> >>>
> >>>>> Yes, but making a mogstored node out of it is a bad idea.
> >>>> I'm using nginx as a mogstored frontend without problems.
> >>>
> >>> It wasn't about nginx, it was about using nginx+mogilefs module as
> >>> storage node.
> >>>
> >>>> Tuqui
> >>>> Valery Kholodkov さんは書きました:
> >>>>> 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 grid.net.ru> wrote:
> >>>>>>> This is to use nginx as a frontend to MogileFS and hide
> >>>>>>> interaction with the tracker while store files.
> >>>>>>>
> >>>>>>> ----- Michael Shadle <mike503 at gmail.com> 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 grid.net.ru
> >>>>>>>>> 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 grid.net.ru> 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
> >>>>>>>>>>> (gadu-gadu.pl
> >>>>>>>>>>> ).
> >>>>>>>>>>> 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:
> >>>>>>>>>>> http://www.grid.net.ru/nginx/mogilefs.en.html
> >>>>>>>>>>>
> >>>>>>>>>>> Feel free to contact me if you have problems with this!
> >>>>>
> >>>
> >>>
> >>> -- 
> >>> Best regards,
> >>> Valery Kholodkov
> >>>
> >>
> >
> >
> > -- 
> > Best regards,
> > Valery Kholodkov
> >
> 

-- 
-- 
Regards,
Valery Kholodkov