-
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
Unify AddSpilledUrl into UpdateObjectLocationBatch RPC #23872
Conversation
<< " and object directory has been informed"; | ||
} | ||
}); | ||
object_directory_->ReportObjectSpilled(object_id, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be thread safe since it's running in the io_service thread. @rkooo567 Could you double check here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah. If this is used within the node manager io service (main_service_
in object manager), it should be okay. (so I think it should be thread-safe now)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, good to see code being removed!
@@ -877,6 +877,63 @@ TEST_F(SingleNodeTest, TestObjectInterface) { | |||
ASSERT_TRUE(results[1]->IsException()); | |||
} | |||
|
|||
TEST_F(SingleNodeTest, TestHandleUpdateObjectLocationBatch) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah thanks for adding this test, but I think the existing Python tests are probably enough for this PR... I've actually been meaning to deprecate this test suite since the maintainability is not really worth the test coverage compared to e2e integration tests.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also iirc, this test doesn't even run in the master CI!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yea, I also realized that. Also the current core_worker_test is like semi integration test, it needs to launch gcs, raylet, etc. We should try to make it more unit-testable via techniques like dependency ingestion.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! A couple small comments
@@ -877,6 +877,63 @@ TEST_F(SingleNodeTest, TestObjectInterface) { | |||
ASSERT_TRUE(results[1]->IsException()); | |||
} | |||
|
|||
TEST_F(SingleNodeTest, TestHandleUpdateObjectLocationBatch) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also iirc, this test doesn't even run in the master CI!
src/ray/object_manager/test/ownership_based_object_directory_test.cc
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, this looks good! Left some minor comments.
I noticed the PR also includes FIFO location updates now; could you update the PR description to include that and also add a C++ test?
|
Why are these changes needed?
Related issue number
Checks
scripts/format.sh
to lint the changes in this PR.