Description of problem: Files which are HOT are getting demoted from the hot tier. Version-Release number of selected component (if applicable): master How reproducible: 1) create a dist-rep volume 1x2 2) start the volume 3) switch off the performance xlator (optional) 4) attach a dist-rep tier 1x2 5) fuse mount the volume 6) create a file : touch file1. 7) heat up the file : for i in {1..10}; do touch file1; done 8) wait for the default promotion/demotion frequency secs i.e sleep 120 9) the file demoted! [shouldn't demote!!] 10) Heat up the file again: for i in {1..10}; do touch file1; done 11) wait for the default promotion/demotion frequency secs i.e sleep 120 12) the file is promoted [as expected] 13) heat up the file : for i in {1..10}; do touch file1; done 14) wait for the default promotion/demotion frequency secs i.e sleep 120 15) the file demoted! [shouldn't demote!!] Actual results: HOT file Demoted! Expected results: HOT File shouldn't demote Additional info:
REVIEW: http://review.gluster.org/11577 (libgfdb/sql: Fixing broken query of find_unchanged) posted (#1) for review on master by Joseph Fernandes
*** Bug 1240926 has been marked as a duplicate of this bug. ***
COMMIT: http://review.gluster.org/11577 committed in master by Vijay Bellur (vbellur) ------ commit 79106a754d4804074e5c5c6bfe1c388f7d314535 Author: Joseph Fernandes <josferna> Date: Wed Jul 8 14:35:45 2015 +0530 libgfdb/sql: Fixing broken query of find_unchanged The find_unchanged query should be "write_heat <= defined_heat" AND "read_heat <= defined_heat" and not "write_heat <= defined_heat" OR "read_heat <= defined_heat" Change-Id: Ie82e02aafbb7ea14563007307de3350ea022049a BUG: 1240970 Signed-off-by: Joseph Fernandes <josferna> Reviewed-on: http://review.gluster.org/11577 Reviewed-by: Dan Lambright <dlambrig> Reviewed-by: mohammed rafi kc <rkavunga> Tested-by: NetBSD Build System <jenkins.org> Tested-by: Joseph Fernandes Tested-by: Dan Lambright <dlambrig> Tested-by: Gluster Build System <jenkins.com>
Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.
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