[checkmk-commits] 6031 FIX Improved initial activation step performance in some cases

Module: check_mk Branch: master Commit: 3b71c921a9145bb3259b78758060a984a4ca8722 URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=3b71c921a9145b… Author: Lars Michelsen <lm(a)mathias-kettner.de> Date: Wed Apr 25 09:41:10 2018 +0200 6031 FIX Improved initial activation step performance in some cases When activating the changed configuration, the first step "Initializing activation" may take a lot of time when there are a lot of files located below the "local" hierarchy of the site. This is caused by a backup mechanism that is executed in this step. It saves snapshots of your WATO configuration (not the whole site nor the whole config of the site) to archives which are located below "var/check_mk/wato/snapshots". These can be used for reverting the changes in the GUI and for recovery of configuration files. This is not primarily a backup mechanism, better use the Check_MK site backup for this task. These archives were also containing the whole local/ hierarchy. In case there are a lot of small files or some larger files in this hierarchy, this slowed down the activation significantly. We've decided to remove those files from the config snapshot now. Change-Id: Ib215fa78ef16f03f2e17d294478d62b98e2d6f9e --- .werks/6031 | 23 +++++++++++++++++++++++ web/plugins/wato/backup_domains.py | 1 - 2 files changed, 23 insertions(+), 1 deletion(-) diff --git a/.werks/6031 b/.werks/6031 new file mode 100644 index 0000000..5357ee8 --- /dev/null +++ b/.werks/6031 @@ -0,0 +1,23 @@ +Title: Improved initial activation step performance in some cases +Level: 1 +Component: wato +Class: fix +Compatible: compat +Edition: cre +State: unknown +Version: 1.6.0i1 +Date: 1524641789 + +When activating the changed configuration, the first step "Initializing activation" may +take a lot of time when there are a lot of files located below the "local" hierarchy of +the site. + +This is caused by a backup mechanism that is executed in this step. It saves snapshots +of your WATO configuration (not the whole site nor the whole config of the site) to +archives which are located below "var/check_mk/wato/snapshots". These can be used for +reverting the changes in the GUI and for recovery of configuration files. This is not +primarily a backup mechanism, better use the Check_MK site backup for this task. + +These archives were also containing the whole local/ hierarchy. In case there are a lot +of small files or some larger files in this hierarchy, this slowed down the activation +significantly. We've decided to remove those files from the config snapshot now. diff --git a/web/plugins/wato/backup_domains.py b/web/plugins/wato/backup_domains.py index e877c14..83399e8 100644 --- a/web/plugins/wato/backup_domains.py +++ b/web/plugins/wato/backup_domains.py @@ -76,6 +76,5 @@ watolib.backup_domains.update({ ("dir", "var/check_mk/packages" ), ("dir", "local" ), ], - "default" : True, }, })