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

DB & MQ retry logic #13

Closed
juhtornr opened this issue Jan 2, 2019 · 3 comments · Fixed by #88
Closed

DB & MQ retry logic #13

juhtornr opened this issue Jan 2, 2019 · 3 comments · Fixed by #88
Assignees
Labels
version 2 Task saved for version 2

Comments

@juhtornr
Copy link
Contributor

juhtornr commented Jan 2, 2019

Issue by silverdaz
Monday Dec 10, 2018 at 18:35 GMT
Originally opened as NBISweden/LocalEGA#381


Improve the robustness of the DB and MQ connections

@juhtornr juhtornr added this to the Sprint 41 milestone Jan 2, 2019
@juhtornr
Copy link
Contributor Author

juhtornr commented Jan 2, 2019

Comment by juhtornr
Thursday Dec 20, 2018 at 08:17 GMT


@silverdaz Makes sense but can you be little bit more specific? What is the problem at the moment?

@silverdaz
Copy link
Contributor

For example, when the message broker is restarted, all the connected components lose their connection and crash.
The retry logic is ready, but not merged.

@juhtornr
Copy link
Contributor Author

Time estimate: 2 days

@silverdaz silverdaz added the version 2 Task saved for version 2 label Feb 20, 2019
@silverdaz silverdaz mentioned this issue Dec 13, 2019
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
version 2 Task saved for version 2
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants