Gracefully handle node primary transitions in provisioner #69
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As-is, transitioning the primary node while a provisioner task is running can have undefined results. Investigate this in more detail and correct in an optimal way.
mentioned in issue #68
The only real option I can think of is to block node primary transition if a job is running in the provisioner. This is not ideal, since there could still be queued jobs that would then be discarded without implementing some sort of Redis mirroring or a non-Redis datastore (not currently supported unfortunately, PostgreSQL support for Celery was dropped) and could delay needed transitions for an arbitrary amount of time, but would still be a valid solution to the immediate problem.
Other options might be possible that require more work, so feedback requested.
mentioned in commit
74ff8b41ea
Implemented a warning in the CLI for primary/secondary commands. Otherwise, this can remain as-is for the foreseeable future.
closed