+++ This bug was initially created as a clone of Bug #1218717 +++ When a file is migrated, it should stay on the destination tier for a full "cycle", meaning it should not immediately be moved based on timing on the destination tier. --- Additional comment from Dan Lambright on 2015-06-03 09:06:20 EDT --- This problem occurs if two nodes start at different times. Each node should run promotion/demotion at the same time. --- Additional comment from Anand Avati on 2015-06-06 01:17:44 EDT --- REVIEW: http://review.gluster.org/11110 (tier/dht: Fixing non atomic promotion/demotion w.r.t to frequency period) posted (#1) for review on master by Joseph Fernandes (josferna) --- Additional comment from Anand Avati on 2015-06-07 00:01:34 EDT --- REVIEW: http://review.gluster.org/11110 (tier/dht: Fixing non atomic promotion/demotion w.r.t to frequency period) posted (#2) for review on master by Joseph Fernandes (josferna) --- Additional comment from Anand Avati on 2015-06-08 05:54:46 EDT --- REVIEW: http://review.gluster.org/11110 (tier/dht: Fixing non atomic promotion/demotion w.r.t to frequency period) posted (#3) for review on master by Joseph Fernandes (josferna) --- Additional comment from Anand Avati on 2015-06-11 06:56:00 EDT --- REVIEW: http://review.gluster.org/11110 (tier/dht: Fixing non atomic promotion/demotion w.r.t to frequency period) posted (#4) for review on master by Joseph Fernandes (josferna)
REVIEW: http://review.gluster.org/11191 (tier/dht: Fixing non atomic promotion/demotion w.r.t to frequency period) posted (#1) for review on release-3.7 by Joseph Fernandes (josferna)
REVIEW: http://review.gluster.org/11191 (tier/dht: Fixing non atomic promotion/demotion w.r.t to frequency period) posted (#3) for review on release-3.7 by Joseph Fernandes
REVIEW: http://review.gluster.org/11191 (tier/dht: Fixing non atomic promotion/demotion w.r.t to frequency period) posted (#4) for review on release-3.7 by Niels de Vos (ndevos)
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.3, please open a new bug report. glusterfs-3.7.3 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/12078 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user