Ticket #994 (new enhancement)
reconfig by graceful failover
|Reported by:||dustin||Owned by:|
A few alternatives to reconfiguration came up in IRC.
One particularly attractive model is to treat a reconfig as a time to spin up a new member of the master pool, then gracefully disconnect each slave on the "retiring" master when it finishes a build.
This obviously has a lot of prerequisites, but it would be a great model:
- fully db-based
- fully-baked master failover support
- abstracted status so you're not looking at two web statuses during the changeover