high availability of rundeck web app
Reported by Esa | September 14th, 2011 @ 10:46 AM
Make rundeck able to be run in a 'hot/hot' or 'hot/standby' configuration where there are at least two instances of rundeck. Both aware of the 'universal state' of the rundeck state.
Goal being at least able to have quick failover (in case of host crash, etc.) from primary to secondary instance.
This has a lot of ramifications, it is likely acceptable that a running job (job that is running when the host dies) would fail. But, for example, any queued jobs, or other scheduled jobs, would be executed on the 'new primary machine'.
This is pretty much a classic 'leader/slave setup example'.
No comments found
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
(DEPRECATED) Please use github issues for issue tracking at http://github.com/dtolabs/rundeck/issues
Esa