+++ This bug was initially created as a clone of Bug #1222126 +++ +++ This bug was initially created as a clone of Bug #1221747 +++ Description of problem: With the feature http://review.gluster.org/#/c/7702/ the on disk layout would now carry 0 in the first 4 bytes of the xattr trusted.glusterfs.dht. In previous revisions this was set to 1 and the DHT code does a strict check on the same. As a result lookups would fail to read and throw layout errors, when older clients are used against a 3.7 volume. Version-Release number of selected component (if applicable): 3.7 How reproducible: Always Steps to Reproduce: 1. Access a gluster volume using client bits from 3.7 2. Create a directory 3. Access the created directory from a client using 3.6 client bits Actual results: Step 3 reports layout inconsistencies Expected results: Step 3 should not report layout inconsistencies Additional info: Fixing this has a few parts to it as follows, - Do not set layout xattr with the commit-hash unless lookup-unhashed is set to auto - Do not allow older clients to connect if the above option is set - Warn the administrator that setting lookup-unhashed to auto would cause older clients to not function well with the volume --- Additional comment from Anand Avati on 2015-05-15 16:02:21 EDT --- REVIEW: http://review.gluster.org/10797 (dht: Change lookup-unhashed 'auto' to a new option) posted (#1) for review on master by Shyamsundar Ranganathan (srangana) --- Additional comment from Anand Avati on 2015-05-20 16:37:46 EDT --- REVIEW: http://review.gluster.org/10797 (dht: Change lookup-unhashed 'auto' to a new option) posted (#2) for review on master by Shyamsundar Ranganathan (srangana) --- Additional comment from Anand Avati on 2015-05-22 09:59:24 EDT --- REVIEW: http://review.gluster.org/10797 (dht: Change lookup-unhashed 'auto' to a new option) posted (#4) for review on master by Shyamsundar Ranganathan (srangana) --- Additional comment from Anand Avati on 2015-05-22 15:11:53 EDT --- REVIEW: http://review.gluster.org/10797 (dht: Add lookup-optimize configuration option for DHT) posted (#5) for review on master by Shyamsundar Ranganathan (srangana) --- Additional comment from Anand Avati on 2015-05-28 00:19:06 EDT --- REVIEW: http://review.gluster.org/10797 (dht: Add lookup-optimize configuration option for DHT) posted (#6) for review on master by Raghavendra G (rgowdapp)
REVIEW: http://review.gluster.org/10976 (dht: Add lookup-optimize configuration option for DHT) posted (#2) for review on release-3.7 by Shyamsundar Ranganathan (srangana)
REVIEW: http://review.gluster.org/10976 (dht: Add lookup-optimize configuration option for DHT) posted (#3) for review on release-3.7 by Shyamsundar Ranganathan (srangana)
The required changes to fix this bug have not made it into glusterfs-3.7.1. This bug is now getting tracked for glusterfs-3.7.2.
REVIEW: http://review.gluster.org/10976 (dht: Add lookup-optimize configuration option for DHT) posted (#4) for review on release-3.7 by Shyamsundar Ranganathan (srangana)
REVIEW: http://review.gluster.org/10976 (dht: Add lookup-optimize configuration option for DHT) posted (#5) for review on release-3.7 by Shyamsundar Ranganathan (srangana)
COMMIT: http://review.gluster.org/10976 committed in release-3.7 by Raghavendra G (rgowdapp) ------ commit bedda7c258e000d94b09599340400955e4b8079f Author: Shyam <srangana> Date: Fri May 15 15:50:42 2015 -0400 dht: Add lookup-optimize configuration option for DHT Currently with commit 4eaaf5 a mixed version cluster would have issues if lookup-uhashed is set to auto, as older clients would fail to validate the layouts if newer clients (i.e 3.7 or upwards) create directories. Also, in a mixed version cluster rebalance daemon would set commit hash for some subvolumes and not for the others. This commit fixes this problem by moving the enabling of the functionality introduced in the above mentioned commit to a new dht option. This option also has a op_version of 3_7_1 thereby preventing it from being set in a mixed version cluster. It brings in the following changes, - Option can be set only if min version of the cluster is 3.7.1 or more - Rebalance and mkdir update the layout with the commit hashes only if this option is set, hence ensuring rebalance works in a mixed version cluster, and also directories created by newer clients do not cause layout errors when read by older clients - This option also supersedes lookup-unhased, to enable the optimization for lookups more deterministic and not conflict with lookup-unhashed settings. Option added is cluster.lookup-optimize, which is a boolean. Usage: # gluster volume set VOLNAME cluster.lookup-optimize on Change-Id: Ifd1d4ce3f6438fcbcd60ffbfdbfb647355ea1ae0 BUG: 1225940 Signed-off-by: Shyam <srangana> Reviewed-on: http://review.gluster.org/10976 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: N Balachandran <nbalacha> Reviewed-by: Raghavendra G <rgowdapp> Tested-by: Raghavendra G <rgowdapp>
*** Bug 1221747 has been marked as a duplicate of this bug. ***
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.2, please reopen this bug report. glusterfs-3.7.2 has been announced on the Gluster Packaging mailinglist [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://www.gluster.org/pipermail/packaging/2015-June/000006.html [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user