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

feature request: high availability mode #275

Closed
pmlopes opened this issue Jun 30, 2014 · 4 comments
Closed

feature request: high availability mode #275

pmlopes opened this issue Jun 30, 2014 · 4 comments

Comments

@pmlopes
Copy link

pmlopes commented Jun 30, 2014

Sometimes I would like to have a simple HA container, that in case it terminates with a status code other than 0 would relaunch with the same args it used before.

Imagine that you have a python/nodejs app and there was an exception, the node/python process dies and if the flag ha is true then fig would issue again a up command.

This would be a very simple HA feature but good enough for most of deployment scenarios...

@bfirsh
Copy link

bfirsh commented Jun 30, 2014

Related: moby/moby#26

@d11wtq
Copy link

d11wtq commented Jul 5, 2014

Personally I think this is not the responsibility of fig. Fig is an orchestration tool, not a monitoring tool. Just my $0.02. In particular, fig doesn't keep running. It just hits endpoints in the docker API and then returns. I like that. I'd prefer to see this sort of thing added to docker itself, although running any one of the multitude of available process monitors out there (God, Monit, Supervisor, Bluepill) inside the container is quite feasible.

@pmlopes
Copy link
Author

pmlopes commented Jul 21, 2014

sorry for the late reply, if i get it right docker should only containerize a process starting multiple processes is possible that that is the the main idea. What i meant with HA was not really monitoring in the sense of hows the process doing but just simple start and stop events which could trigger running some scripts...

I think this would be very useful for most deployed applications...

@dnephin dnephin closed this as completed Sep 1, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants