Description of problem: No synchronization is needed for a single subvolume DHT in most of the fops and DHT can act as pass through. One important codepath is rename as synchronization cost is high. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: https://review.gluster.org/19817 (cluster/dht: act as passthrough for renames on single child DHT) posted (#1) for review on master by Raghavendra G
COMMIT: https://review.gluster.org/19817 committed in master by "Raghavendra G" <rgowdapp> with a commit message- cluster/dht: act as passthrough for renames on single child DHT Various synchronization present in dht_rename while handling directories and files is necessary only if we have more than only one child. Change-Id: Ie21ad419125504ca2f391b1ae2e5c1d166fee247 fixes: bz#1563511 Signed-off-by: Raghavendra G <rgowdapp>
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 [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/announce/2018-June/000102.html [2] https://www.gluster.org/pipermail/gluster-users/