This repository has been archived by the owner on Jan 15, 2019. It is now read-only.
[dev.icinga.com #471] don't clean live/config data on core startup (NEBTYPE_PROCESS_PRELAUNCH) #237
Labels
Milestone
This issue has been migrated from Redmine: https://dev.icinga.com/issues/471
Created by mfriedrich on 2010-06-02 15:15:04 +00:00
Assignee: mfriedrich
Status: Resolved (closed on 2010-06-02 21:10:04 +00:00)
Target Version: 1.0.2
Last Update: 2010-06-02 21:10:04 +00:00 (in Redmine)
basically speaking, it's not always clear what ido2db tries to do during startup.
especially the startup of the core, where the callbacks send all new and updated config data over to the database.
normally, if this state is being reached and the realtime data is too old (seconds), ido2db will try to clear all realtime and all config tables.
Furthermore there's a relationship between several config objects getting cleaned and the objects table, where all config objects are updated to is_active=0.
So, the question is how to prevent those cleanups and let the user decide what he really needs.
The decision, which config gets to ido2db, is done in idomod.cfg and the config_output_options.
But the decision being made for clearing the tables is just based on the core startup.
The proposed patch is to add 2 new config options, which are set default to 1, enabling the cleanup.
clean_realtime_tables_on_core_startup=1
clean_config_tables_on_core_startup=1
The user can then decide, which of those should be disabled (enabled is the default, also if those options are not set in older ido2db.cfg).
Changesets
2010-06-02 16:55:29 +00:00 by mfriedrich 6d0f795
Relations:
The text was updated successfully, but these errors were encountered: