You can disable it, we were using that option to work around a caching issue earlier.
That bug has been fixed now.# gluster volume set <VOL> performance.strict-write-ordering off
-KrutikaOn Thu, Apr 14, 2016 at 8:27 AM, Lindsay Mathieson <lindsay.mathieson@xxxxxxxxx> wrote:
On 14 April 2016 at 12:53, Lindsay Mathieson
<lindsay.mathieson@xxxxxxxxx> wrote:
> With 3.7.6 (and 3.7.7?) with sharded volumes we had to set:
> performance.strict-write-ordering: on
> otherwise we got wildly inconsistent file sizes between node mounts.
> However I've been rechecking it with 3.7.9 and that no longer seems to
> be the case, whcih is good as strict-write-ordering was quite a
> performance hit.
>
> Is this the case? has the issue been fixed for 3.7.9?
ps. If strict-write-ordering is no longer needed can I just turn it
off? or would I have to recreate the files on the volume?
thanks,
--
Lindsay
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
