Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shmem3c: auth update for memmgr change #33

Merged
merged 13 commits into from
Jun 7, 2014
Merged

Shmem3c: auth update for memmgr change #33

merged 13 commits into from
Jun 7, 2014

Conversation

jinmei
Copy link
Contributor

@jinmei jinmei commented Jun 3, 2014

also an incremental update. the actual change is bbb94be and e89181e (the latter is a small fix, not directly related to the main change).

…r restart

reader/writer versions of mapped files are now persisted in a file and will
be used on (re)start of memmer.
some more initial states and related methods were added.
this can fail if the data were corrupted, and it's not good to let
the thread die due to the exception.  we now catch this and try to
re-create a new segment, or at least report the error to the main
thread.
also completed other small TODOs, mainly documentation.
…when not.

This can happen in normal initialization, i.e., both the authoritative
server and the memory manager just starts.  This initial reset command
is just for segment reader modules to be synchronized with the memory
manager, and the actual reset will be delayed until the memory manager
completes building the segment data with any un-applied updates.
this will be needed if memmgr fails to initialize the segment data on
restart, while reader modules are currently somehow using the segment.
in this case memmgr will send a segment info update to reset the
segment for synchronization, and, as a result, readers will fail to use
the segment until it's fixed.  that's not good, but this should be a rare
erroneous condition and should be acceptable.
this can happen due to DB locking if DDNS is heavily updating it.
it now also catches an exception from install().  this can happen
if the locking issue happens in the delayed apply of zone diffs.
… shmem3

Fixed Conflicts:
	src/lib/python/bundy/memmgr/tests/builder_tests.py
jinmei added a commit that referenced this pull request Jun 7, 2014
Shmem3c: auth update for memmgr change
@jinmei jinmei merged commit 3cab947 into master Jun 7, 2014
@jinmei
Copy link
Contributor Author

jinmei commented Jun 7, 2014

merging to move forward. I'll create separate issues for the outstanding review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant