Gluster users - Jan 2017 - performance.flush-behind

Option: performance.flush-behind
Default Value: on
Description: If this option is set ON, instructs write-behind translator 
to perform flush in background, by returning success (or any errors, if 
any of previous  writes were failed) to application even before flush 
FOP is sent to backend filesystem.


Does this mean that essentially fsync is disabled by default?


-- 
Lindsay Mathieson

On 8/01/2017 10:38 AM, Lindsay Mathieson wrote:
> Option: performance.flush-behind
> Default Value: on
> Description: If this option is set ON, instructs write-behind 
> translator to perform flush in background, by returning success (or 
> any errors, if any of previous  writes were failed) to application 
> even before flush FOP is sent to backend filesystem.
>
>
> Does this mean that essentially fsync is disabled by default?
>
Also:

performance.write-behind : on
performance.strict-o-direct : off


It would appear that by default, fsync and O_DIRECT are off, and 
write-behind is on

-- 
Lindsay Mathieson