[Gluster-users] Configuration suggestions (aka poor/slow performance on new hardware)
Tom Lanyon
tom at netspot.com.au
Wed Mar 31 05:14:34 UTC 2010
On 31/03/2010, at 2:36 PM, Raghavendra G wrote:
> Current design of write-behind acknowledges writes (to applications) even
> when they've not hit the disk. Can you please explain how this design is
> different (if it is different) from the idea you've explained above?
Is this gluster method of write-behind acknowledging the writes before they've left the client? The method Ed was describing is that the write is acknowledged only once its reached the server (and a defined number of replication targets), even though it hasn't hasn't been written to disk on the server yet. This is a hybrid approach which safeguards against client power failure before the write (which has already been acknowledged) gets pushed to any servers, but improves performance over end-to-end write-through as it does not wait for the write acknowledgement from the physical disk(s).
Please correct me if I am mistaken. :)
Tom
More information about the Gluster-users
mailing list