Re: [Pacemaker] Postresql streaming replication support
On Wed, Jan 9, 2013 at 12:56 PM, Keith Ouellette keith.ouelle...@airgas.com wrote: Now I am trying to get that integrated with pacemaker. In my searches, I see that pacemaker with DRBD seems to be the prevelant implementation an most documentation was written around that. However, due to our network conditions, I am looking for information on doing this with WAL. I did find a resource agent that was wirtten for what I am doing ( https://github.com/t-matsuo/resource-agents/wiki/Resource-Agent-for-PostgreSQL-9.1-streaming-replication). The issue is the example if complex with the explanation written only toward that example. Is there another place that I can get documentation on this resource agent? Is there another way that this could be accmoplished that someone has tried? Keith we are using the above resource agent in production with streaming replication. Do you have any specific questions about its usage? -- Jesse Hathaway, Systems Engineer Braintree http://getbraintree.com 917-418-8423 ___ 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
Re: [Pacemaker] Multi-state slave resource promoted when node was not quorate, expected?
On Mon, Dec 17, 2012 at 7:19 PM, Andrew Beekhof and...@beekhof.net wrote: No. That sounds like a bug. Can you attach a crm_report tarball to a bugzilla entry please? Thanks Andrew, Bug reported created, please let me know if you need any other diagnostic information: https://developerbugs.linuxfoundation.org/show_bug.cgi?id=2663 -- Jesse Hathaway, Systems Engineer Braintree http://getbraintree.com 917-418-8423 ___ 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
[Pacemaker] Multi-state slave resource promoted when node was not quorate, expected?
We had a switch failure and all the nodes were partitioned. The slave node promoted its resource while it did not have quorum. We have no-quourm-policy set to freeze. Is it expected for resource promotion to occur when a node does not have quorum? -- Jesse Hathaway, Systems Engineer Braintree http://getbraintree.com 917-418-8423 ___ 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
[Pacemaker] Upgrading a master salve resource agent, Maintenance best practices
We need to change a parameter in our Postgres Master Slave resource. Unfortunately the version of the resource agent we are running does not support a reload action. As a consequence Pacemaker wants to restart the resource. This is not acceptable as it will try to demote the master as well as restart the slave. Are there any methods to upgrade a resource agent in this type of situation without necessitating a restart? More broadly what tools or documentation should we look towards for these types of surgical maintenance operations on our pacemaker clusters? -- Jesse Hathaway, Systems Engineer Braintree http://getbraintree.com ___ 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
Re: [Pacemaker] Upgrading a master salve resource agent, Maintenance best practices
On Mon, Nov 19, 2012 at 12:55 PM, David Vossel dvos...@redhat.com wrote: I do not have much experience managing pacemaker deployments, but this is what I would try. Set the resource option, is-managed, to false. http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-resource-options.html Go in and make whatever changes you need to make to both the cib and the active resource. After you are done, set the resource's is-managed option back to true, or remove it from the config entirely since the default is true. Alternatively you could set the entire cluster in maintenance mode by setting the cluster option, maintenance-mode, to true. This will automatically make all the resources un-managed until maintenance mode is turned off again. Unfortunately, placing the resource or cluster into maintenance mode does not help, since when the resource is managed again pacemaker notices that the resource has changed and the policy engine makes any necessary actions, e.g. in this case restarting the resource. -- Jesse Hathaway, Systems Engineer Braintree http://getbraintree.com 917-418-8423 ___ 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
Re: [Pacemaker] Upgrading a master salve resource agent, Maintenance best practices
On Mon, Nov 19, 2012 at 1:42 PM, David Vossel dvos...@redhat.com wrote: What version of pacemaker are you using? We are using 1.1.5-01e86afaaa6d4a8c4836f68df80ababd6ca3902f If parameters are marked as re-loadable and the resource agent supports a reload action that the resource will only be reloaded: http://www.clusterlabs.org/doc/en-US/Pacemaker/1.0/html/Pacemaker_Explained/s-reload.html Unfortunately the resource agent we are using, pgsql, does not have a reload action. -- Jesse Hathaway, Systems Engineer Braintree http://getbraintree.com 917-418-8423 ___ 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
