AFR locking options

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

 



Dear All,

I have a question regarding the number of lock servers required for a
2 node setup.
Both nodes can run software that write data, but never at the same
time (controlled via cluster software).
If I understand the text correct on:

http://www.gluster.com/community/documentation/index.php/Understanding_AFR_Translator#Write_algorithm
and
http://www.mail-archive.com/gluster-devel at nongnu.org/msg06707.html

Is it advisable to increase the number of lock servers to ensure that
when the first node in the subvolume fails the other node can continue
to work correctly even if the first node comes back?
Text at "Locking options":
These options let you specify the number of lock servers to use for
each class of file operations. The default values are satisfactory in
most cases. If you are extra paranoid, you may want to increase the
values [more info requested: what are the benefits and drawbacks to
doing this].

2nd question:
What happens if the first node holds a lock on a file and fails (power
down or kernel panic)? What if the second node now wants to modify
this file?


Kind regards,
Richard


[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