REVIEW: https://review.gluster.org/21337 (cluster/afr: Batch writes in same lock even when multiple fds are open) posted (#1) for review on release-5 by Pranith Kumar Karampuri
COMMIT: https://review.gluster.org/21337 committed in release-5 by "Shyamsundar Ranganathan" <email@example.com> with a commit message- cluster/afr: Batch writes in same lock even when multiple fds are open
When eager-lock is disabled because of multiple-fds opened and app
writes come on conflicting regions, the number of locks grows very
fast leading to all the CPU being spent just in locking and unlocking
by traversing huge queues in locks xlator for granting locks.
Reduce the number of locks in transit by bundling the writes in the
same lock and disable delayed piggy-pack when we learn that multiple
fds are open on the file. This will reduce the size of queues in the
locks xlator. This also reduces the number of network calls like
Please note that this problem can still happen if eager-lock is
disabled as the writes will not be bundled in the same lock.
Signed-off-by: Pranith Kumar K <firstname.lastname@example.org>
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-5.0, please open a new bug report.
glusterfs-5.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.