Description of problem: There is scope for improvement of translators that get loaded in the brick and change the order of translators in the graph. This bug will track all changes needed for that effort. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/9521 (mgmt/glusterd: Refactor brick graph generation in volgen) posted (#5) for review on master by Vijay Bellur (vbellur)
REVIEW: http://review.gluster.org/9751 (mgmt/glusterd: Refactor brick graph generation in volgen.) posted (#1) for review on master by Vijay Bellur (vbellur)
COMMIT: http://review.gluster.org/9751 committed in master by Krishnan Parthasarathi (kparthas) ------ commit d1397dbd7d6cdbd2d81d5d36d608b6175d449db4 Author: Vijay Bellur <vbellur> Date: Wed Feb 25 20:34:41 2015 +0530 mgmt/glusterd: Refactor brick graph generation in volgen. This commit does the following: 1. Adds several new functions for generation of brick xlator units in a volgen. Each such function takes care of generation of only one xlator in volgen. 2. A new table, server_graph_table, links all individual graph generation functions together. The order of xlator function generators in the table determines the topology of the brick graph. 3. server_graph_builder() invokes individual graph generators by walking through server_graph_table. Addition of debug xlators into the brick graph is also handled by this walk. As a result, a lot of cruft that is present in the exisiting implementation of this function gets cleaned up. 4. get_server_xlator() now makes use of server_graph_table to determine whether a xlator key corresponds to a server xlator or not. Change-Id: I46bb6e331544150302eb5b33c4007917aff2586d BUG: 1188196 Signed-off-by: Vijay Bellur <vbellur> Reviewed-on: http://review.gluster.org/9751 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Krishnan Parthasarathi <kparthas> Tested-by: Krishnan Parthasarathi <kparthas>
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