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

_migrateStartCloneTransaction should have a longer lock wait timeout #1168

Closed
leifwalsh opened this issue May 28, 2014 · 0 comments
Closed
Assignees
Milestone

Comments

@leifwalsh
Copy link
Contributor

Didn't notice it until testing on a more severely loaded system, but update_during_migrate and delete_during_migrate get lock timeouts with what's sure to be an annoying frequency. We do need to make the per-client lock wait timeout workable, and use it here.

@leifwalsh leifwalsh added this to the 1.5.0 milestone May 28, 2014
@leifwalsh leifwalsh self-assigned this May 28, 2014
leifwalsh added a commit that referenced this issue May 28, 2014
not exposed as user command yet, but probably should
leifwalsh added a commit that referenced this issue May 28, 2014
not exposed as user command yet, but probably should
leifwalsh added a commit that referenced this issue May 28, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant