On Tue, Nov 20, 2012 at 10:57 AM, Jesse Hathaway
wrote:
> On Mon, Nov 19, 2012 at 1:42 PM, David Vossel 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 suppor
On Mon, Nov 19, 2012 at 1:42 PM, David Vossel 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://ww
- Original Message -
> From: "Jesse Hathaway"
> To: "The Pacemaker cluster resource manager"
> Sent: Monday, November 19, 2012 1:06:34 PM
> Subject: Re: [Pacemaker] Upgrading a master salve resource agent, Maintenance
> best practices
>
>
>
On Mon, Nov 19, 2012 at 12:55 PM, David Vossel 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-opt
- Original Message -
> From: "Jesse Hathaway"
> To: pacemaker@oss.clusterlabs.org
> Sent: Monday, November 19, 2012 9:03:57 AM
> Subject: [Pacemaker] Upgrading a master salve resource agent, Maintenance
> best practices
>
>
> We need to change a para
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 resta
