Eager-lock is now giving better performance in block after (https://github.com/gluster/glusterfs/issues/418) so it is advised to use eager-lock on with the newer versions of gluster-block.
REVIEW: https://review.gluster.org/19913 (block-profile: enable cluster.eager-lock in block-profile) posted (#2) for review on master by Pranith Kumar Karampuri
COMMIT: https://review.gluster.org/19913 committed in master by "Niels de Vos" <firstname.lastname@example.org> with a commit message- block-profile: enable cluster.eager-lock in block-profile
Eager-lock gave 2.5X perf improvement. On top of that with batching
fix in tcmu-runner and client-io-threads we are seeing close to 3X perf
improvement. But we don't want to include that in the default profile
option but enable it on a case by case basis. So not adding
Signed-off-by: Prasanna Kumar Kalever <email@example.com>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-v4.1.0, please open a new bug report.
glusterfs-v4.1.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.