[SPAM?] read consistency amongst bricks / sync writes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Vincent.

I believe that if your volumes are setup as mirrored (as replicated or replicated-distribute) the file will exist on as many bricks as are designated by the number of copies (replica) requested when the volume is created. E.g

volume create NEW-VOLNAME replica 2 NEW-BRICK ...

In the case of the volume being replicated-distribute, if the file is not found on server b, it will make a call to server a to get it, and pass it to the gluster client without it having any knowledge of where it was actually located.

Clear as mud? :-)

James Burnash, Unix Engineering

-----Original Message-----
From: gluster-users-bounces at gluster.org [mailto:gluster-users-bounces at gluster.org] On Behalf Of Vincent Thomasset
Sent: Tuesday, April 19, 2011 11:34 AM
To: gluster-users at gluster.org
Subject: [SPAM?] read consistency amongst bricks / sync writes
Importance: Low

Hi,

This is a newbie question as i am relatively new to glusterfs but
nonetheless... :)

I believe the file propagation is asynchronous between the bricks and was
wondering whether a subsequent write to a file and read of that same file could
possibly happen on different bricks, so that the following scenario
would happen:

- write on brick a
- read on brick b (file not found)

Or, in a different fashion, if it would be possible to force sync
writes across all
bricks (with the obvious performance hit) to avoid the latter scenario ?

This is using glusterfs 3.1.1.

Thank you,
Vincent
_______________________________________________
Gluster-users mailing list
Gluster-users at gluster.org
http://gluster.org/cgi-bin/mailman/listinfo/gluster-users


DISCLAIMER:
This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this in error, please immediately notify me and permanently delete the original and any copy of any e-mail and any printout thereof. E-mail transmission cannot be guaranteed to be secure or error-free. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission.
NOTICE REGARDING PRIVACY AND CONFIDENTIALITY Knight Capital Group may, at its discretion, monitor and review the content of all e-mail communications. http://www.knight.com


[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux