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.

Sign up for GitHub

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

Jump to bottom

Stop pipeline doesn't work with multi node setup #59

Closed
lispyclouds opened this issue Oct 26, 2019 · 0 comments
Closed

Stop pipeline doesn't work with multi node setup #59

lispyclouds opened this issue Oct 26, 2019 · 0 comments
Labels
bug hammock

Comments

@lispyclouds
Copy link
Member

lispyclouds commented Oct 26, 2019 •
edited
Loading

Similar to #26, when a stop pipeline request is received in a multi node setup, its possible that the node is actually running the relevant container may not be the one that received the request.
@lispyclouds lispyclouds mentioned this issue Oct 26, 2019
Closed
lispyclouds added a commit that referenced this issue Oct 29, 2019
@lispyclouds
Manage distributed state sync
9744648 
- Add triggers and LISTEN to Postgres events on change of pipeline state
- Add ability to react to state changes and coordinate among nodes
- Implement this for pipeline stop
- Remove stopped? column and rely only on status
- Add new state 'stopped'
- Amend tests
- Add deps to achieve this
- Add scaled bob-nodes to docker-compose with NGINX
- Run integration tests with 3 replica bob cluster
- Add stopping integration tests
- Amend CircleCI tests
- Closes #59 #60
lispyclouds added a commit that referenced this issue Oct 29, 2019
@lispyclouds
Manage distributed state sync
587324a 
- Add triggers and LISTEN to Postgres events on change of pipeline state
- Add ability to react to state changes and coordinate among nodes
- Implement this for pipeline stop
- Remove stopped? column and rely only on status
- Add new state 'stopped'
- Amend tests
- Add deps to achieve this
- Add scaled bob-nodes to docker-compose with NGINX
- Run integration tests with 3 replica bob cluster
- Add stopping integration tests
- Amend CircleCI tests
- Closes #59 #60
lispyclouds added a commit that referenced this issue Oct 30, 2019
@lispyclouds
Manage distributed state sync
2d917d2 
- Add triggers and LISTEN to Postgres events on change of pipeline state
- Add ability to react to state changes and coordinate among nodes
- Implement this for pipeline stop
- Remove stopped? column and rely only on status
- Add new state 'stopped'
- Amend tests
- Add deps to achieve this
- Add scaled bob-nodes to docker-compose with NGINX
- Run integration tests with 3 replica bob cluster
- Add stopping integration tests
- Amend CircleCI tests
- Closes #59 #60
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug hammock
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lispyclouds