On 2019-07-12 6:03 p.m., Josep Maria Viñolas wrote: > Hi, > > I don't know if it is possible to decide to start resource A in one node > and then start another resource B avoiding the node where resource A has > been started.
I think you want to look at anti-colocation. > In the end what we need is to have a four node cluster that will have > drbd9 and pacemaker will mount a resource (auto promoting it to master) > in one node also starting an nfs server and exporting that resource to > the other three nodes. Then pacemaker should start a nfs filesystem > mount from that master node on the other three nodes, but avoiding to > start the mount in the master node as that master node already has the > resource mounted and accessible. > > I know I could mount the resource in another folder, export it and then > mount it with nfs in all nodes in the correct mount point, even in the > master node that will export and mount the resource at the same time. > But I'm trying to avoid mounting from the same node that exports it, as > the performance will be affected (I assume). > > Any thoughts? -- Digimer Papers and Projects: https://alteeve.com/w/ "I am, somehow, less interested in the weight and convolutions of Einstein’s brain than in the near certainty that people of equal talent have lived and died in cotton fields and sweatshops." - Stephen Jay Gould _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
