-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
[Core] make StringIdMap thread safe #22893
Merged
scv119
merged 2 commits into
ray-project:master
from
alipay:make_string_id_map_thread_safe
Mar 8, 2022
Merged
[Core] make StringIdMap thread safe #22893
scv119
merged 2 commits into
ray-project:master
from
alipay:make_string_id_map_thread_safe
Mar 8, 2022
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
wumuzi520
changed the title
make StringIdMap thread safe
[WIP][Core] make StringIdMap thread safe
Mar 8, 2022
wumuzi520
force-pushed
the
make_string_id_map_thread_safe
branch
4 times, most recently
from
March 8, 2022 05:55
b21c836
to
fd4d631
Compare
scv119
reviewed
Mar 8, 2022
wumuzi520
force-pushed
the
make_string_id_map_thread_safe
branch
2 times, most recently
from
March 8, 2022 06:21
8872efe
to
fc65966
Compare
wumuzi520
changed the title
[WIP][Core] make StringIdMap thread safe
[Core] make StringIdMap thread safe
Mar 8, 2022
wumuzi520
force-pushed
the
make_string_id_map_thread_safe
branch
from
March 8, 2022 08:25
61e3ca5
to
744e3b8
Compare
microbenchmark result:
|
scv119
approved these changes
Mar 8, 2022
What's |
ha C++ unit tests |
6 tasks
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.
Why are these changes needed?
Another PR(#22817) refactoring the legacy resource data structure from
ResourceSet
toResourceRequest
and fromSchedulingResources
toNode
, which depends onscheduling::ResourceID
.But, the
StringIdMap
is wrapped byThreadPrivate
insideBaseSchedulingID
, which means thescheduling::ResourceID
andscheduling::NodeID
can only be visited in one single thread. However, many C++ UTs have such a scenario: restarting the GCS server multiple times in the same process, each restart will reset theGcsServer
object and change a new thread, which will cause multiple threads to access StringIdMap in the different time.Beside, the GCS may have multi-threads in the future, it is possible that in the future there will be multiple threads accessing the
StringIdMap
So, this PR make
StringIdMap
thread safe.Related issue number
Checks
scripts/format.sh
to lint the changes in this PR.