Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This patch implements transparent update. It prevents downtimes or void results each time a new configuration is pushed.
The deleted objects state is saved when new initial Broks are sent by a scheduler. Queries get executed from this saved state until new objects are fully loaded. Once done, the old state is erased, and queries are made from latest objects state.
To enable transparent update, set the
transparent_update
parameter to1
in the livestatus configuration:Also:
itersorted
bound method in regenerator class that crashed livestatus when a query was made during objects reloading. If an id could not be found, return a void list rather than crashing the whole module.__itersorted__
method at initialization to avoid uglyobject has no attribute '__itersorted__'
exceptions when service starts.