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

Fixing component migration #3164

Merged
merged 1 commit into from Feb 12, 2018
Merged

Fixing component migration #3164

merged 1 commit into from Feb 12, 2018

Conversation

sithhell
Copy link
Member

  • Simplified migration handling in primary namespace
  • Fixing various race conditions

hpx::future<bool> end_migration_async(naming::id_type const& id);
std::pair<naming::id_type, naming::address>
begin_migration(naming::id_type const& id);
bool end_migration(naming::id_type const& id);
Copy link
Member

Choose a reason for hiding this comment

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

These operations are potentially remote. What was your rationale to change this to run synchronously?

Copy link
Member Author

Choose a reason for hiding this comment

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

The main rationale was that those two functions were always executed on the components service locality. Remote execution never happened in the migration implementation we have.

Copy link
Member

Choose a reason for hiding this comment

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

Yes, you're right - thanks.

Copy link
Member

@hkaiser hkaiser left a comment

Choose a reason for hiding this comment

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

Very nice, thanks!

 - Simplified migration handling in primary namespace
 - Fixing various race conditions
@msimberg msimberg mentioned this pull request Feb 12, 2018
28 tasks
@msimberg msimberg merged commit ef7360b into master Feb 12, 2018
@hkaiser hkaiser deleted the fix_migration branch February 12, 2018 17:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants