On 3 November 2013 14:24, Takatoshi MATSUO <matsuo....@gmail.com> wrote:
> Hi Richard > > 2013/11/3 Richard Colley <rcol...@cardaccess.com.au>: > >> > >> This ? > >> > >> > https://github.com/t-matsuo/resource-agents/wiki/Resource-agent-for-postgresql-9.2-for-disaster(split)-site > >> > >> You can use rep_mode="slave". > >> > >> Takatoshi MATSUO > >> > > > > Hi Takatoshi, that helps a lot. > > > > How would you cutover between sites? It seems like I'd need to delete > the > > resources at each site, and re-create them. > > I think it's possible using a ticket. > > > Are there any risks doing that? > > About deleting primitive resources and creating master/slave resource > manually ? > It means building a new cluster, so I think it does not have many risks. > > > Or is there some easier way to cutover? Do you see no benefit in the > mysql > > ra approach of using a ticket to identify the active vs passive site? > > No, I don't. > I have never used mysql RA as master/slave resource. > > > > > Thanks, > > Richard > > Regards, > Takatoshi Thanks again for your help Takatoshi. But I'm still a bit uncertain how to proceed with cutover. What should I do when promoting a site to the active one? What should I do when demoting a site to the passive one? If I use rep_mode=(a)sync on the active site, then when demoting it to passive, I need to delete my pgsql & vip resources, and create new resources in rep_mode=slave? Similarly on passive site - delete pgsql & vip and create new resources in rep_mode=(a)sync? Or is there some way to do this without deleting and re-creating resources on each site? Can I trigger this by granting/revoking a ticket? Thanks, Richard
_______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
