Fast reload #1015
Open
Fast reload #1015
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
responding to DNS requests.
…tes and can continue byte by byte. Also it can continue after an interrupt.
forward_add and forward_delete should be distributed to other processes, but when threaded, they should not be distributed to other threads because the structure is not thread specific any more.
with timing and memory use output.
…that resources are not held by the threads and can be deleted.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 implements fast_reload. It reloads the unbound server and does not stop the processing of queries. So that service of queries remains uninterrupted by the reload process.
It can be used with
unbound-control fast_reload. This then reloads the server. Cache is kept from before the reload to after. Also existing queries are kept, and the state machines continue to work on them after the reload. Only some options are changed, global options from the config structure, and forwards, and stubs.The fast_reload works by creating a thread that reads config, and allocates memory. Then it quickly halts the other threads, updates the config and swaps the trees of forwards and stubs in place, and continues the other threads. A test with thousands of forwards, has a reload time of 0.027s with 0.0003s spent in halting the other threads.