Skip to content
GitLab
Projects
Groups
Snippets
/
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
Sebastian Schrader
Kea
Commits
e3e92f01
Commit
e3e92f01
authored
Aug 02, 2013
by
Mukund Sivaraman
Browse files
[2856] Add a comment about add_reader() in states other than READY
parent
786a742b
Changes
1
Hide whitespace changes
Inline
Side-by-side
src/lib/python/isc/memmgr/datasrc_info.py
View file @
e3e92f01
...
...
@@ -131,7 +131,15 @@ class SegmentInfo:
that are using the "current" reader version of the segment. It
must be called by memmgr when it first gets the pre-existing
readers or when it's notified of a new reader. No state
transition happens."""
transition happens.
When the SegmentInfo is not in the READY state, if memmgr gets
notified of a new reader (such as b10-auth) subscribing to the
readers group and calls add_reader(), we assume the new reader
is using the new mapped file and not the old one. For making
sure there is no race, memmgr should make SegmentInfo updates in
the main thread itself (which also handles communications) and
only have the builder in a different thread."""
if
reader_session_id
in
self
.
__readers
:
raise
SegmentInfoError
(
'Reader session ID is already in readers set: '
+
str
(
reader_session_id
))
...
...
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment