[Gluster-devel] eager locks

[Krishnan Parthasarathi]

Emmanuel,

You could confirm that the clients are indeed have eager-lock feature enabled
by looking at the client's log file.

We have the volume file used by the client/mount process written to the log file,
before transitioning to the configurations present in that volume file.
You could look for "eager-lock" being present in that portion of the client's log file.

Hope that helps,
Krish

----- Original Message -----
> I am testing eager locks on glusterfs-3.5.0qa3 / NetBSD 6.1.2, and they
> seem to work (we disabled them by default for NetBSD on 3.4 release
> because they were broken).
> 
> How can I be sure the client is using them? On a brick I can do that:
> # gluster volume info gfs351
>  
> Volume Name: gfs351
> Type: Distributed-Replicate
> Volume ID: d8420bcf-2434-4f77-a39d-37348a9b3645
> Status: Started
> Number of Bricks: 2 x 2 = 4
> Transport-type: tcp
> Bricks:
> Brick1: silo:/export/wd2a
> Brick2: hangar:/export/wd1a
> Brick3: hangar:/export/wd3a
> Brick4: debacle:/export/wd1a
> Options Reconfigured:
> cluster.eager-lock: on
> 
> But how can I probe the config client side?
> 
> --
> Emmanuel Dreyfus
> http://hcpnet.free.fr/pubz
> manu at netbsd.org
> 
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at nongnu.org
> https://lists.nongnu.org/mailman/listinfo/gluster-devel
>