Description of problem: 3.7.1 is already released and the DHT lookup-optimize feature is not a part of the same. As a result the minimum op-version needed for lookup-optimize to work needs to be incremented to 3.7.2.
REVIEW: http://review.gluster.org/11073 (cluster/dht: Increment op-version for lookup-optimize to 3.7.2) posted (#1) for review on master by Shyamsundar Ranganathan (srangana)
REVIEW: http://review.gluster.org/11073 (cluster/dht: Increment op-version for lookup-optimize to 3.7.2) posted (#2) for review on master by N Balachandran (nbalacha)
COMMIT: http://review.gluster.org/11073 committed in master by Raghavendra G (rgowdapp) ------ commit ce2488ac2a1a9b7944373676595b0d579e4b75f1 Author: Shyam <srangana> Date: Wed Jun 3 14:12:27 2015 -0400 cluster/dht: Increment op-version for lookup-optimize to 3.7.2 3.7.1 has already shipped, so carrying this configuration option at that op-version will break compatibility. As a result bumping this to 3.7.2. Change-Id: I603d82184ec10d0ea3edf550490e960a8523d572 BUG: 1227894 Signed-off-by: Shyam <srangana> Reviewed-on: http://review.gluster.org/11073 Reviewed-by: N Balachandran <nbalacha> Reviewed-by: Raghavendra G <rgowdapp> Tested-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-3.8.0, please open a new bug report. glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user