2013/4/5 Steven Bambling :
> I've done some basic testing with your path and it looks to work like a charm.
>
> I've also confirmed that upon loosing a sync hot standby postgresql will just
> wait forever for a sync hot standby to come back online to complete the
> transaction. To the client is
I've done some basic testing with your path and it looks to work like a charm.
I've also confirmed that upon loosing a sync hot standby postgresql will just
wait forever for a sync hot standby to come back online to complete the
transaction. To the client is looks like a "stuck" connection.
On Apr 4, 2013, at 8:08 AM, Takatoshi MATSUO
mailto:matsuo@gmail.com>> wrote:
Hi Steven
I made a patch as a trial.
https://github.com/t-matsuo/resource-agents/commit/bd3b587c6665c4f5eba0491b91f83965e601bb6b#heartbeat/pgsql
This patch never show "STREAMING|POTENTIAL".
Thanks,
Takatoshi MAT
Hi Steven
I made a patch as a trial.
https://github.com/t-matsuo/resource-agents/commit/bd3b587c6665c4f5eba0491b91f83965e601bb6b#heartbeat/pgsql
This patch never show "STREAMING|POTENTIAL".
Thanks,
Takatoshi MATSUO
2013/4/4 Takatoshi MATSUO :
> Hi Steven
>
> Sorry for late reply
>
> 2013/3/29 S
Hi Steven
Sorry for late reply
2013/3/29 Steven Bambling :
> Taskatoshi/Rainer thanks so much for the quick responses and clarification.
>
> In response to the rep_mode being set to sync.
>
> If the master is running the monitor check as low as every 1s, then its
> updating the nodes with the "n
ameter
>> node_list (hopefully your node names in Pacemaker are the same as in
>> node_list) and compares them to get the highest.
>> If the highest is this list is the own one, it sets the master-score to
>> 1000, on other nodes to 100.
>> Pacemaker then selects the node
highest is this list is the own one, it sets the master-score to
> 1000, on other nodes to 100.
> Pacemaker then selects the node with the highest master score and promote
> this.
>
> Rainer
> Gesendet: Mittwoch, 27. März 2013 um 14:37 Uhr
> Von: "Steven Bambling"
> An
n Bambling"
An: "The Pacemaker cluster resource manager"
Betreff: Re: [Pacemaker] PGSQL resource promotion issue
On Mar 28, 2013, at 8:13 AM, Rainer Brestan <rainer.bres...@gmx.net> wrote:
Hi Steve,
i think, you have misunderstood how ip addresses are used with
g" mailto:smbambl...@arin.net>>
An: "The Pacemaker cluster resource manager"
mailto:pacemaker@oss.clusterlabs.org>>
Betreff: Re: [Pacemaker] PGSQL resource promotion issue
In talking with andreask from IRC, I miss understood the need to include the
op monitor. I figured it
2013 um 14:37 Uhr
Von: "Steven Bambling"
An: "The Pacemaker cluster resource manager"
Betreff: Re: [Pacemaker] PGSQL resource promotion issue
In talking with andreask from IRC, I miss understood the need to include the op monitor. I figured it was pulled from the resource scr
In talking with andreask from IRC, I miss understood the need to include the
op monitor. I figured it was pulled from the resource script by default.
I used pcs to add the new attributes and one was then promoted to master
pcs resource add_operation PGSQL monitor interval=5s role=Master
pcs r
11 matches
Mail list logo
