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

Daemon workers do not automatically recreate lost connection #1822

Closed
sphuber opened this issue Jul 30, 2018 · 1 comment
Closed

Daemon workers do not automatically recreate lost connection #1822

sphuber opened this issue Jul 30, 2018 · 1 comment
Assignees
Labels
Milestone

Comments

@sphuber
Copy link
Contributor

sphuber commented Jul 30, 2018

Due to the limited heartbeat timeout that is set by the default configuration of the RabbitMQ server (see #1821), the connection of daemon workers are often closed by the server. Currently, the worker does not seem to be able to automatically reopen its connection

@sphuber sphuber added type/bug priority/critical-blocking must be resolved before next release topic/workflows labels Jul 30, 2018
@sphuber sphuber added this to the v1.0.0 milestone Jul 30, 2018
@sphuber sphuber self-assigned this Jul 30, 2018
@muhrin
Copy link
Contributor

muhrin commented Oct 3, 2018

Again as with #1821 this should be fixed by plumpy v0.11. This one is perhaps even more tricky to test as it requires externally forcing a connection drop and checking if the connection comes back. I think we should really push this back to kiwipy as it is responsible for making sure that the communicator reconnects itself. If this works, plumpy and aiida should also.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants