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

Stop vendoring pyarrow #7233

Merged
merged 3 commits into from
Feb 20, 2020
Merged

Conversation

simon-mo
Copy link
Contributor

@simon-mo simon-mo commented Feb 19, 2020

This will be the final revert.

Check the diff here f5d1571

@AmplabJenkins
Copy link

Can one of the admins verify this patch?

_exit(kRayletStoreErrorExitCode);
if (exit_on_error_) {
// When shutting down a cluster, it's possible that the plasma store is killed
// earlier than raylet, in this case we don't want raylet to crash, we instead
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
// earlier than raylet, in this case we don't want raylet to crash, we instead
// earlier than raylet. In this case we don't want raylet to crash, we instead

<< "Problem communicating with the object store from raylet, check logs or "
<< "dmesg for previous errors: " << boost_to_ray_status(error).ToString();
if (exit_on_error_) {
RAY_LOG(FATAL)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a reason we RAY_LOG(FATAL) here, but _exit in the other code block?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i don't know the reason

@@ -71,6 +77,8 @@ class ObjectStoreNotificationManager {
int64_t num_removes_processed_;
std::vector<uint8_t> notification_;
local_stream_protocol::socket socket_;

bool exit_on_error_;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please document (what happens if this is false?).

// Exit raylet process.
_exit(kRayletStoreErrorExitCode);
} else {
return;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we log an error message here?

ObjectStoreNotificationManager(boost::asio::io_service &io_service,
const std::string &store_socket_name);
const std::string &store_socket_name,
bool exit_on_error = true);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not a strong preference, but I think it would be good to make this an explicit argument instead of optional.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah this is a special case I want to keep backward compatibility.

@AmplabJenkins
Copy link

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Ray-PRB/22140/
Test FAILed.

@simon-mo
Copy link
Contributor Author

@stephanie-wang addressed

Copy link
Contributor

@edoakes edoakes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@AmplabJenkins
Copy link

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Ray-PRB/22144/
Test FAILed.

@simon-mo
Copy link
Contributor Author

Test memory scheduling seems to be flaky on master

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.

4 participants