Description of problem:
This should give more precise timestamp that indicates *exactly* when graph switch took place and hopefully help with some of the graph-switch related bugs that the users are reporting in future.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
REVIEW: http://review.gluster.org/16365 (mount/fuse: Fix the place where graph-switch event is logged) posted (#1) for review on release-3.9 by Krutika Dhananjay (firstname.lastname@example.org)
COMMIT: http://review.gluster.org/16365 committed in release-3.9 by Pranith Kumar Karampuri (email@example.com)
Author: Krutika Dhananjay <firstname.lastname@example.org>
Date: Wed Dec 28 14:32:12 2016 +0530
mount/fuse: Fix the place where graph-switch event is logged
Backport of: http://review.gluster.org/16302
Signed-off-by: Krutika Dhananjay <email@example.com>
Smoke: Gluster Build System <firstname.lastname@example.org>
NetBSD-regression: NetBSD Build System <email@example.com>
Reviewed-by: Raghavendra G <firstname.lastname@example.org>
CentOS-regression: Gluster Build System <email@example.com>
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.9.1, please open a new bug report.
glusterfs-3.9.1 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.