Files are of the type promotefile-<pid> and demotefile-<pid>. Every time a new rebalance daemon is started a new pair of files is created, old ones are not necessarily deleted.

REVIEW: http://review.gluster.org/11931 (cluster/tier: avoid filling /var/run with tiering files) posted (#1) for review on master by Dan Lambright (dlambrig)

REVIEW: http://review.gluster.org/11931 (cluster/tier: avoid filling /var/run with tiering files) posted (#2) for review on master by Dan Lambright (dlambrig)

REVIEW: http://review.gluster.org/11931 (cluster/tier: avoid filling /var/run with tiering files) posted (#4) for review on master by Dan Lambright (dlambrig)

REVIEW: http://review.gluster.org/11931 (cluster/tier: avoid filling /var/run with tiering files) posted (#5) for review on master by Dan Lambright (dlambrig)

REVIEW: http://review.gluster.org/11931 (cluster/tier: avoid filling /var/run with tiering files) posted (#6) for review on master by Dan Lambright (dlambrig)

REVIEW: http://review.gluster.org/11931 (cluster/tier: avoid filling /var/run with tiering files) posted (#7) for review on master by Dan Lambright (dlambrig)

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