Re: [Moosefs-users] The implementation of append operation in MFS

[Ken <ken...@gm...>]

I'm not an expert of moose source code, but some detail maybe help.
client communicate with master and chunk server in write like:
 client -> master: inode, chunk index*     # CUTOMA_FUSE_WRITE_CHUNK
 master -> client: length, chunk id, chunk server location

 client <-> chunk server: ...

 client -> master: chunkid, inode, length # CUTOMA_FUSE_WRITE_CHUNK_END
 master -> client: OK

It's a long transaction, then master know file size is growing.

* chunk index: is calculate from write offset.

-Ken




On Fri, Oct 14, 2011 at 6:14 PM, A.S. nagle <a.s...@ho...> wrote:
> Dear all
> This is nagle, a new bie to MFS, I was wondering the implementation of
> append operation in MFS:
> Consider about this:
> 1) A client want to create a very small file, then master allocates 64KB for
> it.
> 2) The client writes so much for many times
> 3) The size of file reaches the 64KB, but the client still wants to write
> much more, i name it as append operation.
> 4) In this situation, the client may find that the space is used up, then it
> ask the master for much more space, then, what is going on?
> Does any one give me a hint, thank you very much,
> Best regards,
> Nagle,
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2d-oct
> _______________________________________________
> moosefs-users mailing list
> moo...@li...
> https://lists.sourceforge.net/lists/listinfo/moosefs-users
>
>