Blame SOURCES/rsyslog-8.24.0-doc-rhbz1696686-imjournal-fsync.patch

ff08e8
From 3ba46e563a3a5384fd6d783a8315273c237cb6af Mon Sep 17 00:00:00 2001
ff08e8
From: Jiri Vymazal <jvymazal@redhat.com>
ff08e8
Date: Tue, 23 Jul 2019 12:47:09 +0200
ff08e8
Subject: [PATCH] Documetation for new 'fsync' imjournal option
ff08e8
ff08e8
related to #3762 main repo PR
ff08e8
---
ff08e8
 source/configuration/modules/imjournal.rst | 13 +++++++++++--
ff08e8
 1 file changed, 11 insertions(+), 2 deletitions (-)
ff08e8
ff08e8
diff --git a/source/configuration/modules/imjournal.rst b/source/configuration/modules/imjournal.rst
ff08e8
index d8523ae8..47428fc6 100644
ff08e8
--- a/source/configuration/modules/imjournal.rst
ff08e8
+++ b/source/configuration/modules/imjournal.rst
ff08e8
@@ -3,8 +3,7 @@
ff08e8
 
ff08e8
 **Module Name:** imjournal
ff08e8
 
ff08e8
-**Author:** Milan Bartos <mbartos@redhat.com> (This module is **not**
ff08e8
-project-supported)
ff08e8
+**Author:** Milan Bartos <mbartos@redhat.com>
ff08e8
 
ff08e8
 **Available since**: 7.3.11
ff08e8
 
ff08e8
@@ -107,6 +106,16 @@
ff08e8
     with each message to work around this problem. Be aware that in some cases this
ff08e8
     might result in imjournal performance hit.
ff08e8
 
ff08e8
+-  **FSync** [**off**/on]
ff08e8
+
ff08e8
+    When there is a hard crash, power loss or similar abrupt end of rsyslog process,
ff08e8
+    there is a risk of state file not being written to persistent storage or possibly
ff08e8
+    being corrupted. This then results in imjournal starting reading elsewhere then 
ff08e8
+    desired and most probably message duplication. To mitigate this problem you can 
ff08e8
+    turn this option on which will force state file writes to persistent physical 
ff08e8
+    storage. Please note that fsync calls are costly, so especially with lower 
ff08e8
+    PersistStateInterval value, this may present considerable performance hit.
ff08e8
+
ff08e8
 **Caveats/Known Bugs:**
ff08e8
 
ff08e8
 - As stated above, a corrupted systemd journal database can cause major