Re: [Moosefs-users] A question about Mfs's Write process

[Michał B. <mic...@ge...>]

Hi!

 

Thank you for your interest in MooseFS!

 

Writing of each chunks is made independently according to this schema. So if
a file is bigger than 64MB there are two or more such processes working
independently. One finishes writing chunk at position 0 (0B - 64MB) and the
second starts writing at position 1 (64MB - 128MB). It is somehow like two
different files of 64MB were written.

 

 

Kind regards

Michał Borychowski 

MooseFS Support Manager

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Gemius S.A.

ul. Wołoska 7, 02-672 Warszawa

Budynek MARS, klatka D

Tel.: +4822 874-41-00

Fax : +4822 874-41-01

 

 

 

From: lingjie [mailto:li...@gy...] 
Sent: Monday, December 06, 2010 8:14 AM
To: moo...@li...
Subject: [Moosefs-users] A question about Mfs's Write process

 

Dear friend:

 

         Frist , I'm Chinese . My English is just so-so ,and hope you
understanding..

         

         When I browse the http://www.moosefs.org , I discover a picture:

 

 

         This picture is a Moosefs Write process sketch map .Now I hava a
question about it.

         When the Master receive a request from Client, he will assign a
Chunk to connect to Client. And at the second connection ,the Client will
connect to the Chunk to write data .

In the Mfs , using 64MB as a hard-coded chunk size .

         Now, I hava a question . If a data's size greater than 64MB , the
data will be splited , there have a difference :

1.       When the Client and Chunk's connection is builded ,the connection
has established finished until the data transmission .

2.       The Client and Chunk's connection is builded , When the data
achieve 64MB, the connection will disconnect ,and the Client will connect to
Master to recalculate, and reassign a new Chunk to Client, the Chunk maybe
the previous one ,maybe a new one.

 

Above is my question, I hope someone can help me .

If my description is not distinctly ,please contect me. MSN:
sev...@ho...       Email: li...@gy...

         Thanks!