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

Stolon "standby" cluster #157

Closed
sgotti opened this issue Oct 9, 2016 · 5 comments
Closed

Stolon "standby" cluster #157

sgotti opened this issue Oct 9, 2016 · 5 comments
Assignees
Milestone

Comments

@sgotti
Copy link
Member

sgotti commented Oct 9, 2016

For multi datacenter replication (for disaster recovery) a good enhancement will be to be able to create a "standby" stolon cluster where the "master" pg instance (but this definition should be changed) node will be a postgres standby instance following an external pg instance. The other cluster instances will just be standbys of this instance like usual. The external instance can be another stolon cluster with the replication connection string pointing to one stolon proxies or multiple load balanced (or a k8s service) proxies. So we can achieve multi datacenter replicated stolon clusters. Obviously only one of these will be the "master" cluster and the user should manually promote a standby cluster to a master cluster.

Another interesting use case for this feature will be (near) zero downtime migration to a new stolon cluster from another postgres architecture (standalone, another kind of cluster etc...).

stolonctl will add a command to promote the "standby" cluster to a "master" cluster.

@sgotti sgotti added this to the v0.4.0 milestone Oct 9, 2016
@sgotti sgotti self-assigned this Oct 9, 2016
@sgotti sgotti modified the milestones: v0.4.0, v0.5.0 Oct 21, 2016
@sgotti sgotti modified the milestones: v0.5.0, v0.6.0 Dec 12, 2016
@gflarity
Copy link

gflarity commented Mar 19, 2017

@sgotti Could you please give an outline of what would be involved in supporting this and the correct way to go about it? Also an estimate of how long it would take you? This is a feature I'd really like to see and I'd be willing to have one of our devs tackle it.

@sgotti
Copy link
Member Author

sgotti commented Mar 25, 2017

@gflarity The basic idea is to be able to have the "master" instance being a standby of an external instance (than can be any postgresql instance, not only another stolon cluster).

The primary steps will be to be able to have a "master" instance being a standby. For this the basic code should already be in place. There's the need to extend the init mode for initializing the instance as a standby, add some integration tests and add a "promote" command to stolonctl.

I was hoping to work on this in the next weeks but if you want to take a stab at it I'll be very happy to help and review. Thanks!

@gflarity
Copy link

Thanks for the info @sgotti we're still in the process of figuring out how we can best spend our resources here. But we'd really like to help get this feature out sooner. I'll talk it over with the team.

@sgotti
Copy link
Member Author

sgotti commented May 25, 2017

#283 implements this feature.

@sgotti
Copy link
Member Author

sgotti commented May 30, 2017

#283 has been merged.

@sgotti sgotti closed this as completed May 30, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants