From 3af53f8c39181b83cfff4a925cfca8750cfcf465 Mon Sep 17 00:00:00 2001 From: "Kaleb S. KEITHLEY" Date: Mon, 31 Jul 2017 13:32:36 -0400 Subject: doc: release notes for localtime-logging Updates gluster/glusterfs#272 Change-Id: I6f4c19d6986f9e9dbdb3b979715427840512eb10 BUG: 1473826 Signed-off-by: Kaleb S. KEITHLEY Reviewed-on: https://review.gluster.org/17935 Smoke: Gluster Build System Reviewed-by: Shyamsundar Ranganathan Tested-by: Shyamsundar Ranganathan CentOS-regression: Gluster Build System --- doc/release-notes/3.12.0.md | 24 +++++++++++++----------- 1 file changed, 13 insertions(+), 11 deletions(-) diff --git a/doc/release-notes/3.12.0.md b/doc/release-notes/3.12.0.md index 94f97d12c14..52fa0850de7 100644 --- a/doc/release-notes/3.12.0.md +++ b/doc/release-notes/3.12.0.md @@ -15,25 +15,27 @@ feature that you want to describe, and submit the work for review. See, for the respective feature, as "Updates: gluster/glusterfs#N"*** ### Feature one liner -**Notes for users:** - +Add option to use localtime timestamps in log entries **Limitations:** +Gluster defaults to UTC timestamps. glusterd, glusterfsd, and server-side +glusterfs daemons will use UTC until one of a) command line option is +processed, b) gluster config (/var/lib/glusterd/options) is loaded, +c) admin manually sets localtime-logging (cluster.localtime-logging, e.g. +`gluster volume set all cluster.localtime-logging enable`). + +There is no mount option to make the FUSE client enable localtime logging. + +There is no option in gfapi to enable localtime logging. **Known Issues:** +None ## Major issues -1. Expanding a gluster volume that is sharded may cause file corruption - - Sharded volumes are typically used for VM images, if such volumes are - expanded or possibly contracted (i.e add/remove bricks and rebalance) there - are reports of VM images getting corrupted. - - The last known cause for corruption (Bug #1465123) has a fix with this - release. As further testing is still in progress, the issue is retained as - a major issue. - - Status of this bug can be tracked here, #1465123 + +None ## Bugs addressed -Bugs addressed since release-3.11.0 are listed below. \ No newline at end of file -- cgit