+++ This bug was initially created as a clone of Bug #1217786 +++ Description of problem: ctr/libgfdb: Performance enhancer for unlink/create/rename/link fops 1) ctr_link_consistency option for ctr xaltor is provided so that the user can choose to switch it on or off. /* For link consistency we do a double update i.e mark the link * during the wind and during the unwind we update/delete the link. * This has a performance hit. We give a choice here whether we need * link consistency to be spoton or not using link_consistency flag. * This will have only one link update */ 2) In delete the wind time recording is moved to unwind path. /* Special performance case: * Updating wind time in unwind for delete. This is done here * as in the wind path we will not know whether its the last * link or not. For a last link there is not use to update any * wind or unwind time!*/ Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: --- Additional comment from Anand Avati on 2015-05-01 11:57:29 EDT --- REVIEW: http://review.gluster.org/10170 (ctr/libgfdb: Performance enhancer for unlink/create/rename/link fops) posted (#3) for review on master by Joseph Fernandes (josferna) --- Additional comment from Anand Avati on 2015-05-01 12:10:37 EDT --- COMMIT: http://review.gluster.org/10170 committed in master by Kaleb KEITHLEY (kkeithle) ------ commit 4d118cb5ee99b8401d70678fc3b3576ad938999d Author: Joseph Fernandes <josferna> Date: Thu Apr 9 15:07:54 2015 +0530 ctr/libgfdb: Performance enhancer for unlink/create/rename/link fops 1) ctr_link_consistency option for ctr xaltor is provided so that the user can choose to switch it on or off. /* For link consistency we do a double update i.e mark the link * during the wind and during the unwind we update/delete the link. * This has a performance hit. We give a choice here whether we need * link consistency to be spoton or not using link_consistency flag. * This will have only one link update */ 2) In delete the wind time recording is moved to unwind path. /* Special performance case: * Updating wind time in unwind for delete. This is done here * as in the wind path we will not know whether its the last * link or not. For a last link there is not use to update any * wind or unwind time!*/ Change-Id: I209472fb816f939db4a868b97ba053b028f17ea6 BUG: 1217786 Signed-off-by: Joseph Fernandes <josferna> Reviewed-on: http://review.gluster.org/10170 Reviewed-by: Dan Lambright <dlambrig> Tested-by: Gluster Build System <jenkins.com>
REVIEW: http://review.gluster.org/10614 (ctr/libgfdb: Performance enhancer for unlink/create/rename/link fops) posted (#1) for review on release-3.7 by Joseph Fernandes (josferna)
REVIEW: http://review.gluster.org/10614 (ctr/libgfdb: Performance enhancer for unlink/create/rename/link fops) posted (#2) for review on release-3.7 by Joseph Fernandes (josferna)
COMMIT: http://review.gluster.org/10614 committed in release-3.7 by Vijay Bellur (vbellur) ------ commit 42a508fb008c4d2d90faf30616423cfbcba84a30 Author: Joseph Fernandes <josferna> Date: Thu Apr 9 15:07:54 2015 +0530 ctr/libgfdb: Performance enhancer for unlink/create/rename/link fops 1) ctr_link_consistency option for ctr xaltor is provided so that the user can choose to switch it on or off. /* For link consistency we do a double update i.e mark the link * during the wind and during the unwind we update/delete the link. * This has a performance hit. We give a choice here whether we need * link consistency to be spoton or not using link_consistency flag. * This will have only one link update */ 2) In delete the wind time recording is moved to unwind path. /* Special performance case: * Updating wind time in unwind for delete. This is done here * as in the wind path we will not know whether its the last * link or not. For a last link there is not use to update any * wind or unwind time!*/ > http://review.gluster.org/#/c/10170/ > Cherry picked from commit 606d9734543208542afcf9df982bf2d560235ef6 > Change-Id: I209472fb816f939db4a868b97ba053b028f17ea6 > BUG: 1217786 > Signed-off-by: Joseph Fernandes <josferna> > Reviewed-on: http://review.gluster.org/10170 > Reviewed-by: Dan Lambright <dlambrig> > Tested-by: Gluster Build System <jenkins.com> > Signed-off-by: Joseph Fernandes <josferna> Change-Id: I4a89ef80875f36cff91520f712e1f47fde258a63 BUG: 1219066 Signed-off-by: Joseph Fernandes <josferna> Reviewed-on: http://review.gluster.org/10170 Reviewed-by: Dan Lambright <dlambrig> Tested-by: Gluster Build System <jenkins.com> Signed-off-by: Joseph Fernandes <josferna> Reviewed-on: http://review.gluster.org/10614 Tested-by: NetBSD Build System Reviewed-by: Vijay Bellur <vbellur>
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-3.7.0, please open a new bug report. glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user