Occasionally, problems seem to arise where the slon's configuration in-memory falls out of sync with what is stored in the DB.
Thought: As part of the maintenance thread, validate that they are the same.
If any difference is found, dump the in-memory config and the DB config to logs, at some form of debug level. (Possibly warning?) If they are the same, indicate that they agree.
Need to check such things as:
- Node list (sl_node)
- Paths (sl_path)
- Subscriptions (sl_subscribe)
I'm noticing that only the local node's share of sl_path is loaded in, so the data relevant to that is a combination of sl_node+sl_path data.
Branch set up to track this:
Here is a patch which does the compare of sl_node+sl_path to the rtcfg_node structure:
Augmenting with sl_set/sl_subscribe data: