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

ARROW-1788 Fix Plasma store abort bug on client disconnection #1299

Closed

Conversation

stephanie-wang
Copy link
Contributor

No description provided.

auto entry_it = entry.second->clients.find(client);
if (entry_it != entry.second->clients.end()) {
if (entry.second->state == PLASMA_SEALED) {
remove_client_from_object_clients(entry.second.get(), client);
Copy link
Contributor

Choose a reason for hiding this comment

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

As it is with this change, this check is a little asymetric, i.e. remove_client_from_object_clients already checks if the object is from the "right" client, but abort_object doesn't and then here we check in either case. Can you make it more symmetric and handle the checks in the same way? We could have the check in abort_object if we also pass the client and remove it from here.

Copy link
Contributor

@pcmoritz pcmoritz left a comment

Choose a reason for hiding this comment

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

+1 LGTM conditioned on the tests passing

@wesm wesm closed this in 2d34f34 Nov 10, 2017
@stephanie-wang stephanie-wang deleted the plasma-client-disconnect-bug branch November 14, 2017 21:56
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.

2 participants