Re: [ClusterLabs] [ClusterLabs Developers] Resource Agent language discussion

On Wed, 19 Aug 2015 10:59:00 +0200 Jehan-Guillaume de Rorthais j...@dalibo.com wrote: [...] What we tried to achieve with a new pgsql RA: * multistate only (we already have a stateless RA, in bash) * should have a simple code: easier to understand, to maintain, achieve one goal

Re: [ClusterLabs] [ClusterLabs Developers] Resource Agent language discussion

On Tue, 11 Aug 2015 11:30:03 +1000 Andrew Beekhof and...@beekhof.net wrote: On 8 Aug 2015, at 1:14 am, Jehan-Guillaume de Rorthais j...@dalibo.com wrote: Hi Jan, On Fri, 7 Aug 2015 15:36:57 +0200 Jan Pokorný jpoko...@redhat.com wrote: On 07/08/15 12:09 +0200, Jehan

Re: [ClusterLabs] [ClusterLabs Developers] Resource Agent language discussion

On Tue, 11 Aug 2015 06:42:37 +0200 Fabio M. Di Nitto fabbi...@fabbione.net wrote: On 8/7/2015 5:14 PM, Jehan-Guillaume de Rorthais wrote: Hi Jan, On Fri, 7 Aug 2015 15:36:57 +0200 Jan Pokorný jpoko...@redhat.com wrote: On 07/08/15 12:09 +0200, Jehan-Guillaume de Rorthais wrote: Now, I

Re: [ClusterLabs] [ClusterLabs Developers] Resource Agent language discussion

On Tue, 11 Aug 2015 11:15:47 +0200 Fabio M. Di Nitto fabbi...@fabbione.net wrote: [...] In most systems, all commands required to execute a RA in shell are already cached in ram and requirements to re-run them are minimal (and could save a system). with Perl, there was no caching that I

[ClusterLabs] Perl Modules for resource agents (was: Resource Agent language discussion)

Le Thu, 20 Aug 2015 18:21:01 +0200, Jehan-Guillaume de Rorthais <j...@dalibo.com> a écrit : > On Thu, 20 Aug 2015 15:05:24 +1000 > Andrew Beekhof <and...@beekhof.net> wrote: [...] > > > What I was discussing here was: > > > > > > * if not

Re: [ClusterLabs] crm_attribute bug in 1.1.15-rc1

master score set from the RA itself. Try the following command: crm_master -l reboot -r pgsqld -Q or crm_master -l reboot -r pgsqld -N $NODENAME -Q > 2016-05-23 19:00 GMT+03:00 Jehan-Guillaume de Rorthais <j...@dalibo.com>: > > > Le Mon, 23 May 2016 15:42:55 +0300, &

Re: [ClusterLabs] Recovering after split-brain

e kaos. It will always find a way to surprise you. If there is a breach somewhere, soon or later everything will blow up. Regards, -- Jehan-Guillaume de Rorthais Dalibo ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/l

Re: [ClusterLabs] [ClusterLabs Developers] Perl Modules for resource agents (was: Resource Agent language discussion)

A quick top-post. The project moved to its own repository. See: https://github.com/dalibo/PAF/ Any feedback on the perl modules and related questions bellow would still be quite appreciated :) Regards, Le Thu, 26 Nov 2015 01:13:36 +0100, Jehan-Guillaume de Rorthais <j...@dalibo.com> a

[ClusterLabs] why and when a call of crm_attribute can be delayed ?

ogfiles from the three nodes * the content of /var/lib/pacemaker from the three nodes: * CIBs * PEngine transitions Regards, [1] https://github.com/dalibo/PAF -- Jehan-Guillaume de Rorthais Dalibo ___ Users mailing list: Users@clusterlab

Re: [ClusterLabs] crm_attribute bug in 1.1.15-rc1

thinking this patch > https://github.com/ClusterLabs/pacemaker/commit/26d34a9171bddae67c56ebd8c2513ea8fa770204?diff=unified#diff-55bc49a57c12093902e3842ce349a71fR269 > is > not apply in 1.1.15-rc1? > > How I can get integere value from node attribute? With the co

Re: [ClusterLabs] Antw: Re: Informing RAs about recovery: failed resource recovery, or any start-stop cycle?

Le Fri, 20 May 2016 11:12:28 +0200, "Ulrich Windl" <ulrich.wi...@rz.uni-regensburg.de> a écrit : > >>> Jehan-Guillaume de Rorthais <j...@dalibo.com> schrieb am 20.05.2016 um > 09:59 in > Nachricht <20160520095934.029c1822@firost>: > > L

Re: [ClusterLabs] Informing RAs about recovery: failed resource recovery, or any start-stop cycle?

Le Thu, 19 May 2016 10:53:31 -0500, Ken Gaillot a écrit : > A recent thread discussed a proposed new feature, a new environment > variable that would be passed to resource agents, indicating whether a > stop action was part of a recovery. > > Since that thread was long and

Re: [ClusterLabs] crm_attribute bug in 1.1.15-rc1

aster resource. > 2016-05-20 16:40 GMT+03:00 Jehan-Guillaume de Rorthais <j...@dalibo.com>: > > > Le Fri, 20 May 2016 15:31:16 +0300, > > Andrey Rogovsky <a.rogov...@gmail.com> a écrit : > > > > > Hi! > > > I cant get attribute value: >

Re: [ClusterLabs] crm_attribute bug in 1.1.15-rc1

AME -Q (supposing as your resource name is "pgsqld") > 2016-05-23 11:19 GMT+03:00 Jehan-Guillaume de Rorthais <j...@dalibo.com>: > > > Le Mon, 23 May 2016 09:28:41 +0300, > > Andrey Rogovsky <a.rogov...@gmail.com> a écrit : > > > > > I try

Re: [ClusterLabs] crm_attribute bug in 1.1.15-rc1

master resource. Could you show us your configuration please? > 2016-05-23 11:46 GMT+03:00 Jehan-Guillaume de Rorthais <j...@dalibo.com>: > > > Le Mon, 23 May 2016 11:36:37 +0300, > > Andrey Rogovsky <a.rogov...@gmail.com> a écrit : > > > > > Hi >

Re: [ClusterLabs] crm_attribute bug in 1.1.15-rc1

: off > + master-pgsqld : 1 > + pgsql-data-status : STREAMING|ASYNC > > > 2016-05-23 12:35 GMT+03:00 Jehan-Guillaume de Rorthais <j...@dalibo.com>: > > > Le Mon, 23 May 2016 12:31:37 +0300, > > Andrey Rogovsky <a.rogov...@g

Re: [ClusterLabs] Using pacemaker for manual failover only?

Le Tue, 24 May 2016 01:53:22 -0400, Digimer a écrit : > On 23/05/16 03:03 PM, Stephano-Shachter, Dylan wrote: > > Hello, > > > > I am using pacemaker 1.1.14 with pcs 0.9.149. I have successfully > > configured pacemaker for highly available nfs with drbd. Pacemaker > > allows

Re: [ClusterLabs] Pacemaker not invoking monitor after $interval

ction. > > Are there any special conditions under which the monitor will not be > executed? Could you provide us with your Pacemaker setup? > (Cluster IS managed though) Resources can be unmanaged individually as well. Regards, -- Jehan-Guillaume de Rorthais Dalibo _

Re: [ClusterLabs] Antw: Re: Informing RAs about recovery: failed resource recovery, or any start-stop cycle?

Le Fri, 20 May 2016 08:39:42 +0200, "Ulrich Windl" <ulrich.wi...@rz.uni-regensburg.de> a écrit : > >>> Jehan-Guillaume de Rorthais <j...@dalibo.com> schrieb am 19.05.2016 um > >>> 21:29 in > Nachricht <20160519212947.6cc0fd7b@firost>: &g

Re: [ClusterLabs] Informing RAs about recovery: failed resource recovery, or any start-stop cycle?

Le Thu, 19 May 2016 13:15:20 -0500, Ken Gaillot <kgail...@redhat.com> a écrit : > On 05/19/2016 11:43 AM, Jehan-Guillaume de Rorthais wrote: >> Le Thu, 19 May 2016 10:53:31 -0500, >> Ken Gaillot <kgail...@redhat.com> a écrit : >> >>> A recent thre

Re: [ClusterLabs] notify action asynchronous ?

Le Thu, 12 May 2016 11:11:15 -0500, Ken Gaillot <kgail...@redhat.com> a écrit : > On 05/12/2016 04:37 AM, Jehan-Guillaume de Rorthais wrote: > > Le Sun, 8 May 2016 16:35:25 +0200, > > Jehan-Guillaume de Rorthais <j...@dalibo.com> a écrit : > > > >> Le

Re: [ClusterLabs] FR: send failcount to OCF RA start/stop actions

Le Wed, 4 May 2016 13:09:04 +0100, Adam Spiers a écrit : > Hi all, Hello, > As discussed with Ken and Andrew at the OpenStack summit last week, we > would like Pacemaker to be extended to export the current failcount as > an environment variable to OCF RA scripts when they

Re: [ClusterLabs] [Question] About a change of crm_failcount.

On Fri, 3 Feb 2017 09:45:18 -0600 Ken Gaillot wrote: > On 02/02/2017 12:33 PM, Ken Gaillot wrote: > > On 02/02/2017 12:23 PM, renayama19661...@ybb.ne.jp wrote: > >> Hi All, > >> > >> By the next correction, the user was not able to set a value except zero > >> in

Re: [ClusterLabs] [Question] About a change of crm_failcount.

On Thu, 09 Feb 2017 18:04:41 +0100 wf...@niif.hu (Ferenc Wágner) wrote: > Jehan-Guillaume de Rorthais <j...@dalibo.com> writes: > > > PAF use private attribute to give informations between actions. We > > detect the failure during the notify as well, but raise the error

Re: [ClusterLabs] Antw: Re: When the DC crmd is frozen, cluster decisions are delayed infinitely

pacemakerd who feeds the watchdog. If only the crmd is hung, fencing will not > work. Am I correct here? I guess yes. I am talking of a scenario where the server is under a high load (fork bomb, swap storm, ...), not only crmd being hung for some reasons. > -Original Message----- > Fro

Re: [ClusterLabs] ocf scripts shell and local variables

On Mon, 29 Aug 2016 10:02:28 -0500 Ken Gaillot wrote: > On 08/29/2016 09:43 AM, Dejan Muhamedagic wrote: ... >> I doubt that we could do a moderately complex shell scripts >> without capability of limiting the variables' scope and retaining >> sanity at the same time. > >

Re: [ClusterLabs] Antw: Pacemaker 1.1.16 - Release Candidate 1

On Mon, 7 Nov 2016 09:31:20 -0600 Ken Gaillot <kgail...@redhat.com> wrote: > On 11/07/2016 03:47 AM, Klaus Wenninger wrote: > > On 11/07/2016 10:26 AM, Jehan-Guillaume de Rorthais wrote: > >> On Mon, 7 Nov 2016 10:12:04 +0100 > >> Klaus Wenninger <kwenn...@r

Re: [ClusterLabs] Antw: Pacemaker 1.1.16 - Release Candidate 1

On Mon, 7 Nov 2016 12:39:32 -0600 Ken Gaillot <kgail...@redhat.com> wrote: > On 11/07/2016 12:03 PM, Jehan-Guillaume de Rorthais wrote: > > On Mon, 7 Nov 2016 09:31:20 -0600 > > Ken Gaillot <kgail...@redhat.com> wrote: > > > >> On 11/07/2016 03:47 A

Re: [ClusterLabs] Antw: Pacemaker 1.1.16 - Release Candidate 1

On Mon, 7 Nov 2016 10:12:04 +0100 Klaus Wenninger wrote: > On 11/07/2016 08:41 AM, Ulrich Windl wrote: > Ken Gaillot schrieb am 04.11.2016 um 22:37 in > Nachricht > > <27c2ca20-c52c-8fb4-a60f-5ae12f7ff...@redhat.com>: > >> On 11/04/2016

Re: [ClusterLabs] Replicated PGSQL woes

On Wed, 19 Oct 2016 19:44:14 +0900 Keisuke MORI <keisuke.mori...@gmail.com> wrote: > 2016-10-14 18:39 GMT+09:00 Jehan-Guillaume de Rorthais <j...@dalibo.com>: > > On Thu, 13 Oct 2016 14:11:06 -0800 > > Israel Brewster <isr...@ravnalaska.net> wrote: > >

Re: [ClusterLabs] Replicated PGSQL woes

On Fri, 14 Oct 2016 08:10:08 -0800 Israel Brewster <isr...@ravnalaska.net> wrote: > On Oct 14, 2016, at 1:39 AM, Jehan-Guillaume de Rorthais <j...@dalibo.com> > wrote: > > > > On Thu, 13 Oct 2016 14:11:06 -0800 > > Israel Brewster <isr...@ravnalaska.net

Re: [ClusterLabs] Replicated PGSQL woes

On Thu, 13 Oct 2016 14:11:06 -0800 Israel Brewster <isr...@ravnalaska.net> wrote: > On Oct 13, 2016, at 1:56 PM, Jehan-Guillaume de Rorthais <j...@dalibo.com> > wrote: > > > > On Thu, 13 Oct 2016 10:05:33 -0800 > > Israel Brewster <isr...@ravnalaska.net>

Re: [ClusterLabs] Antw: Re: Replicated PGSQL woes

On Fri, 14 Oct 2016 09:59:04 +0200 "Ulrich Windl" <ulrich.wi...@rz.uni-regensburg.de> wrote: > >>> Jehan-Guillaume de Rorthais <j...@dalibo.com> schrieb am 13.10.2016 um > >>> 23:56 in > Nachricht <20161013235606.007018eb@firost>: > >

Re: [ClusterLabs] Replicated PGSQL woes

On Thu, 13 Oct 2016 10:05:33 -0800 Israel Brewster wrote: > On Oct 13, 2016, at 9:41 AM, Ken Gaillot wrote: > > > > On 10/13/2016 12:04 PM, Israel Brewster wrote: [...] > >> But whatever- this is a cluster, it doesn't really matter which node >

[ClusterLabs] setting up SBD_WATCHDOG_TIMEOUT, stonith-timeout and stonith-watchdog-timeout

stonithd, right? "stonith-watchdog-timeout < stonith-timeout". I understand the stonith action timeout should be at least greater than the wdt so stonithd will not raise a timeout before the wdt had a chance to exprire and reset the node. Is it right? Any other comments? Regard

Re: [ClusterLabs] setting up SBD_WATCHDOG_TIMEOUT, stonith-timeout and stonith-watchdog-timeout

On Thu, 8 Dec 2016 11:47:20 +0100 Jehan-Guillaume de Rorthais <j...@dalibo.com> wrote: > Hello, > > While setting this various parameters, I couldn't find documentation and > details about them. Bellow some questions. > > Considering the watchdog module used on a ser

[ClusterLabs] [Announce] PostgreSQL Automatic Failover (PAF) v2.1 rc2 released

dalibo.github.io/PAF/ * http://dalibo.github.io/PAF/documentation.html * https://github.com/dalibo/PAF/issues Please, use the pgsql-general mailing list if you have questions. Any feedback, bug report, patch is welcomed. Regards, -- Jehan-Guillaume de Rorthais Dalibo

Re: [ClusterLabs] setting up SBD_WATCHDOG_TIMEOUT, stonith-timeout and stonith-watchdog-timeout

On Wed, 14 Dec 2016 14:52:41 +0100 Klaus Wenninger <kwenn...@redhat.com> wrote: > On 12/14/2016 01:26 PM, Jehan-Guillaume de Rorthais wrote: > > On Thu, 8 Dec 2016 11:47:20 +0100 > > Jehan-Guillaume de Rorthais <j...@dalibo.com> wrote: > > > >> H

Re: [ClusterLabs] Pacemaker 1.1.16 released

Le 1 décembre 2016 17:39:45 GMT+01:00, Ken Gaillot <kgail...@redhat.com> a écrit : >On 12/01/2016 10:13 AM, Jehan-Guillaume de Rorthais wrote: >> On Wed, 30 Nov 2016 14:05:19 -0600 >> Ken Gaillot <kgail...@redhat.com> wrote: >> >>> ClusterLa

Re: [ClusterLabs] Pacemaker 1.1.16 released

orted only during > rolling upgrades -- nodes with an older version will not be allowed to > rejoin once they shut down.) * how could we get the "CRM feature set" version from the RA? * when this "CRM feature set" has been introduced in Pacema

Re: [ClusterLabs] Pacemaker 1.1.16 released

On Fri, 2 Dec 2016 13:44:59 -0600 Ken Gaillot <kgail...@redhat.com> wrote: > On 12/01/2016 11:58 AM, Jehan-Guillaume de Rorthais wrote: > > > > > > Le 1 décembre 2016 17:39:45 GMT+01:00, Ken Gaillot <kgail...@redhat.com> a > > écrit : > >> On

Re: [ClusterLabs] Status and help with pgsql RA

On Fri, 6 Jan 2017 13:47:34 -0600 Ken Gaillot wrote: > On 12/28/2016 02:24 PM, Nils Carlson wrote: > > Hi, > > > > I am looking to set up postgresql in high-availability and have been > > comparing the guide at > > http://wiki.clusterlabs.org/wiki/PgSQL_Replicated_Cluster

Re: [ClusterLabs] setting up SBD_WATCHDOG_TIMEOUT, stonith-timeout and stonith-watchdog-timeout

On Mon, 19 Dec 2016 13:37:09 +0100 Klaus Wenninger <kwenn...@redhat.com> wrote: > On 12/17/2016 11:55 PM, Jehan-Guillaume de Rorthais wrote: > > On Wed, 14 Dec 2016 14:52:41 +0100 > > Klaus Wenninger <kwenn...@redhat.com> wrote: > > > >> On 12/14/2016 0

[ClusterLabs] pending actions

the cluster startup. What are the consequences if I set cluster-recheck-interval to 30s as instance? Thanks in advance for your lights :) Regards, [1] here is the setup: http://dalibo.github.io/PAF/Quick_Start-CentOS-7.html#cluster-resource-creation-and-management -- Jehan-Guillaume de Rorthais D

Re: [ClusterLabs] [ClusterLabs Developers] checking all procs on system enough during stop action?

On Mon, 24 Apr 2017 17:52:09 +0200 Jan Pokorný <jpoko...@redhat.com> wrote: > On 24/04/17 17:32 +0200, Jehan-Guillaume de Rorthais wrote: > > On Mon, 24 Apr 2017 17:08:15 +0200 > > Lars Ellenberg <lars.ellenb...@linbit.com> wrote: > > > >> On Mo

Re: [ClusterLabs] [ClusterLabs Developers] checking all procs on system enough during stop action?

On Mon, 24 Apr 2017 17:08:15 +0200 Lars Ellenberg <lars.ellenb...@linbit.com> wrote: > On Mon, Apr 24, 2017 at 04:34:07PM +0200, Jehan-Guillaume de Rorthais wrote: > > Hi all, > > > > In the PostgreSQL Automatic Failover (PAF) project, one of most frequent > >

Re: [ClusterLabs] Coming in Pacemaker 1.1.17: start a node in standby

On Thu, 27 Apr 2017 16:07:11 +0200 Lars Ellenberg <lars.ellenb...@linbit.com> wrote: > On Thu, Apr 27, 2017 at 09:19:55AM +0200, Jehan-Guillaume de Rorthais wrote: > > > > > I seem to remember that at some deployment, > > > > > we set the nod

Re: [ClusterLabs] Coming in Pacemaker 1.1.17: start a node in standby

On Tue, 25 Apr 2017 10:33:13 +0200 Lars Ellenberg <lars.ellenb...@linbit.com> wrote: > On Tue, Apr 25, 2017 at 10:27:43AM +0200, Jehan-Guillaume de Rorthais wrote: > > On Tue, 25 Apr 2017 10:02:21 +0200 > > Lars Ellenberg <lars.ellenb...@linbit.com> wrote: > >

Re: [ClusterLabs] Coming in Pacemaker 1.1.17: start a node in standby

On Tue, 25 Apr 2017 10:02:21 +0200 Lars Ellenberg wrote: > On Mon, Apr 24, 2017 at 03:08:55PM -0500, Ken Gaillot wrote: > > Hi all, > > > > Pacemaker 1.1.17 will have a feature that people have occasionally asked > > for in the past: the ability to start a node in

Re: [ClusterLabs] [ClusterLabs Developers] checking all procs on system enough during stop action?

On Mon, 24 Apr 2017 11:27:51 -0500 Ken Gaillot <kgail...@redhat.com> wrote: > On 04/24/2017 10:32 AM, Jehan-Guillaume de Rorthais wrote: > > On Mon, 24 Apr 2017 17:08:15 +0200 > > Lars Ellenberg <lars.ellenb...@linbit.com> wrote: > > > >> On Mo

[ClusterLabs] checking all procs on system enough during stop action?

ld think of is in a shared disk cluster with multiple nodes accessing the same data in RW (such setup can fail in so many ways :)). However, PAF is not supposed to work in such context, so I can live with this. Do you guys have some advices? Do you see some drawbacks? Hazards? Than

Re: [ClusterLabs] How to check if a resource on a cluster node is really back on after a crash

e some feedback and contributors to keep improving it. Do not hesitate to open issues on PAF project if you need to discuss improvements. Regards, -- Jehan-Guillaume de Rorthais Dalibo ___ Users mailing list: Users@clusterlabs.org http://lists.clusterl

Re: [ClusterLabs] PostgreSQL Automatic Failover (PAF) v2.2.0

On Thu, 5 Oct 2017 19:04:52 +0200 Valentin Vidic <valentin.vi...@carnet.hr> wrote: > On Tue, Sep 12, 2017 at 04:48:19PM +0200, Jehan-Guillaume de Rorthais wrote: > > PostgreSQL Automatic Failover (PAF) v2.2.0 has been released on September > > 12th 2017 under the PostgreSQL

[ClusterLabs] Moving PAF to clusterlabs ?

time. Thoughts? [1] http://lists.clusterlabs.org/pipermail/developers/2015-August/66.html [2] http://lists.clusterlabs.org/pipermail/developers/2015-August/68.html Regards, -- Jehan-Guillaume de Rorthais Dalibo ___ Users mailing list: Users

Re: [ClusterLabs] PostgreSQL Automatic Failover (PAF) v2.2.0

On Tue, 12 Sep 2017 08:02:00 -0700 Digimer <li...@alteeve.ca> wrote: > On 2017-09-12 07:48 AM, Jehan-Guillaume de Rorthais wrote: > > PostgreSQL Automatic Failover (PAF) v2.2.0 has been released on September > > 12th 2017 under the PostgreSQL licence. > > > > S

Re: [ClusterLabs] Moving PAF to clusterlabs ?

On Fri, 08 Sep 2017 22:41:47 +0200 Kristoffer Grönlund <kgronl...@suse.com> wrote: > Jehan-Guillaume de Rorthais <j...@dalibo.com> writes: > > > Hi All, > > > > I am currently thinking about moving the RA PAF (PostgreSQL Automatic > > Failover) out

[ClusterLabs] PostgreSQL Automatic Failover (PAF) v2.2.0

ation.html * https://github.com/dalibo/PAF/issues Please, use the pgsql-gene...@postgresql.org or users@clusterlabs.org mailing lists if you have questions. Any feedback is welcomed. Regards, -- Jehan-Guillaume de Rorthais Dalibo ___ Users mailing l

[ClusterLabs] Moving PAF to clusterlabs (was: PostgreSQL Automatic Failover (PAF) v2.2.0)

Hi All, Sorry, this discussion spanned over two different discussions over time...Renaming to the original subject. On Wed, 13 Sep 2017 08:03:14 -0700 Digimer <li...@alteeve.ca> wrote: > On 2017-09-13 07:15 AM, Jehan-Guillaume de Rorthais wrote: > > On Tue, 12 Sep 2017

Re: [ClusterLabs] Antw: Re: Antw: Is there a way to ignore a single monitoring timeout

hers the cluster stack, but soon or later, it will blows something else. Track where the issue comes from, and fix it. -- Jehan-Guillaume de Rorthais Dalibo ___ Users mailing list: Users@clusterlabs.org http://lists.clusterlabs.org/mailman/listinfo/u

Re: [ClusterLabs] PostgreSQL Automatic Failover (PAF) v2.2.0

On Thu, 5 Oct 2017 21:24:36 +0200 Valentin Vidic <valentin.vi...@carnet.hr> wrote: > On Thu, Oct 05, 2017 at 08:55:59PM +0200, Jehan-Guillaume de Rorthais wrote: > > It doesn't seems impossible, however I'm not sure of the complexity around > > this. > > > >

Re: [ClusterLabs] Antw: Re: questions about startup fencing

On Tue, 5 Dec 2017 10:05:03 +0100 Tomas Jelinek <tojel...@redhat.com> wrote: > Dne 4.12.2017 v 17:21 Jehan-Guillaume de Rorthais napsal(a): > > On Mon, 4 Dec 2017 16:50:47 +0100 > > Tomas Jelinek <tojel...@redhat.com> wrote: > > > >> Dne 4.12.2017

Re: [ClusterLabs] Antw: Re: Antw: Re: questions about startup fencing

gt; > <3e60579c-0f4d-1c32-70fc-d207e0654...@redhat.com>: > > > Dne 4.12.2017 v 14:21 Jehan-Guillaume de Rorthais napsal(a): > > > > On Mon, 4 Dec 2017 12:31:06 +0100 > > > > Tomas Jelinek <tojel...@redhat.com> wrote: > > > > > > > >

Re: [ClusterLabs] Antw: Re: questions about startup fencing

n to > complete. (if I understand it correctly ...) > > - Higher-level tools can start or stop all nodes together (e.g. pcs has > pcs cluster start/stop --all). Based on this discussion, I have some questions about pcs: * how is it shutting down the cluster when issuing "pc

Re: [ClusterLabs] Antw: Re: questions about startup fencing

On Mon, 4 Dec 2017 12:31:06 +0100 Tomas Jelinek <tojel...@redhat.com> wrote: > Dne 4.12.2017 v 10:36 Jehan-Guillaume de Rorthais napsal(a): > > On Fri, 01 Dec 2017 16:34:08 -0600 > > Ken Gaillot <kgail...@redhat.com> wrote: > > > >> On Thu, 201

Re: [ClusterLabs] Frequent PAF log messages - Forbidding promotion on in state "startup"

doc: > > https://www.postgresql.org/docs/current/static/monitoring-stats.html#PG-STAT-REPLICATION-VIEW > > > > If you have one standby stuck in "startup" state, that means it was able to > > connect to the master but is not replicating with it for som

Re: [ClusterLabs] Frequent PAF log messages - Forbidding promotion on in state "startup"

On Fri, 11 May 2018 16:25:18 + "Shobe, Casey" wrote: > I'm using PAF and my corosync log ends up filled with messages like this > (about 3 times per minute for each standby node): > > pgsqlms(postgresql-10-main)[26822]: 2018/05/11_06:47:08 INFO: Forbidding >

Re: [ClusterLabs] How to set up fencing/stonith

On Wed, 16 May 2018 21:18:14 +0200 Jehan-Guillaume de Rorthais <j...@dalibo.com> wrote: > On Wed, 16 May 2018 12:43:15 -0600 > Casey & Gina <caseyandg...@icloud.com> wrote: > ... > > fence_vmware - Fence agent for VMWare > > If I remember correctly,

Re: [ClusterLabs] Frequent PAF log messages - Forbidding promotion on in state "startup"

On Mon, 14 May 2018 19:08:47 + "Shobe, Casey" wrote: > > We do not trigger error for such scenario because it would require the > > cluster to react...and there's really no way the cluster can solve such > > issue. So we just put a negative score, which is already

Re: [ClusterLabs] How to set up fencing/stonith

On Wed, 16 May 2018 12:43:15 -0600 Casey & Gina wrote: ... > fence_vmware - Fence agent for VMWare If I remember correctly, this fencing agent is able to connect to vcenter (and/or esxi) to fence a VM. ___ Users mailing list:

Re: [ClusterLabs] Why would a standby node be fenced? (was: How to set up fencing/stonith)

Sorry for getting back to you so late. On Fri, 25 May 2018 11:58:59 -0600 Casey & Gina wrote: > > On May 25, 2018, at 7:01 AM, Casey Allen Shobe > > wrote: > >> Actually, why is Pacemaker fencing the standby node just because a > >> resource fails to start there? I thought only the master

Re: [ClusterLabs] Why would a standby node be fenced? (was: How to set up fencing/stonith)

On Thu, 31 May 2018 22:52:12 +0300 Andrei Borzenkov wrote: > 31.05.2018 22:18, Jehan-Guillaume de Rorthais пишет: > > Sorry for getting back to you so late. > > > > On Fri, 25 May 2018 11:58:59 -0600 > > Casey & Gina wrote: > > > >>&g

Re: [ClusterLabs] Pacemaker PostgreSQL cluster

master somewhere else. Unless you have some session management that are able to wait for the current sessions to finish, then hold the incoming sessions while you are moving the master, you will have downtime and/or xact rollback. Good luck anyway :) -- Jehan-Guillaume de Rorthais

Re: [ClusterLabs] 答复: 答复: Could not start only one node in pacemaker

On Wed, 2 May 2018 05:24:23 + 范国腾 wrote: > Andrei, > > We use the following command to create the cluster: > > pcs cluster auth node1 node2 node3 node4 -u hacluster; > pcs cluster setup --name cluster_pgsql node1 node2 node3 node4; > pcs cluster start --all; > pcs

Re: [ClusterLabs] the PAF switchover does not happen if the VIP resource is stopped

n > node1, it works. The switchover could happened again. > > > Is there any parameter to control this behaviors so that I don't need to > execute the "pcs cleanup" command every time? Check the failcounts for each resource on each nodes (pcs resource failcount [...]). Check the score

Re: [ClusterLabs] the PAF switchover does not happen if the VIP resource is stopped

t and -inf score appears. > 3. ifup the sds1 VIP network card and then ifdown sds2 VIP network card > > [cid:image003.png@01D3DD76.26C5E820] Now failcount and -inf score everywhere. I'm not sure I understand your mail, do you have a question ? > -----邮件原件- > 发件人: Jehan-Guilla

Re: [ClusterLabs] Antw: Re: Antw: Changes coming in Pacemaker 2.0.0

On Thu, 11 Jan 2018 18:32:35 +0300 Andrei Borzenkov wrote: > On Thu, Jan 11, 2018 at 2:52 PM, Ulrich Windl > wrote: > > > > > Andrei Borzenkov schrieb am 11.01.2018 um 12:41 > in > > Nachricht > >

Re: [ClusterLabs] Does anyone use clone instance constraints from pacemaker-next schema?

On Wed, 10 Jan 2018 12:23:59 -0600 Ken Gaillot wrote: ... > My question is: has anyone used or tested this, or is anyone interested > in this? We won't promote it to the default schema unless it is tested. > > My feeling is that it is more likely to be confusing than

Re: [ClusterLabs] Changes coming in Pacemaker 2.0.0

On Wed, 10 Jan 2018 16:10:50 -0600 Ken Gaillot wrote: > Pacemaker 2.0 will be a major update whose main goal is to remove > support for deprecated, legacy syntax, in order to make the code base > more maintainable into the future. There will also be some changes to > default

Re: [ClusterLabs] Changes coming in Pacemaker 2.0.0

On Mon, 15 Jan 2018 11:05:52 -0600 Ken Gaillot <kgail...@redhat.com> wrote: > On Thu, 2018-01-11 at 10:24 -0600, Ken Gaillot wrote: > > On Thu, 2018-01-11 at 01:21 +0100, Jehan-Guillaume de Rorthais wrote: > > > On Wed, 10 Jan 2018 16:10:50 -0600 > > > Ken Ga

Re: [ClusterLabs] Opinions wanted: another logfile question for Pacemaker 2.0

On Mon, 15 Jan 2018 11:19:27 -0600 Ken Gaillot wrote: > On Mon, 2018-01-15 at 18:08 +0100, Klaus Wenninger wrote: > > On 01/15/2018 05:51 PM, Ken Gaillot wrote: > > > Currently, Pacemaker will use the same detail log as corosync if > > > one is > > > specified (as

[ClusterLabs] Misunderstanding or bug in crm_simulate output

Hi list, I was explaining how to use crm_simulate to a colleague when he pointed to me a non expected and buggy output. Here are some simple steps to reproduce: $ pcs cluster setup --name usecase srv1 srv2 srv3 $ pcs cluster start --all $ pcs property set stonith-enabled=false $ pcs

Re: [ClusterLabs] Misunderstanding or bug in crm_simulate output

On Thu, 18 Jan 2018 10:54:33 -0600 Ken Gaillot <kgail...@redhat.com> wrote: > On Thu, 2018-01-18 at 16:15 +0100, Jehan-Guillaume de Rorthais wrote: > > Hi list, > > > > I was explaining how to use crm_simulate to a colleague when he > > pointed to me a

Re: [ClusterLabs] Feedback wanted: changing "master/slave" terminology

function > > vs > > an executing function, an active instance vs a hot-spare instance, > > etc. > > > > That's why I like "promoted"/"started" -- it most directly implies > > "whatever role you get after promote" vs "whatever rol

Re: [ClusterLabs] Feedback wanted: changing "master/slave" terminology

On Fri, 26 Jan 2018 12:41:51 +0300 Vladislav Bogdanov wrote: > 25.01.2018 21:28, Ken Gaillot wrote: > > [...] > > >> If I can throw another suggestion in (without offering preference for > >> it > >> myself), 'dual-state clones'? The reasoning is that, though three > >>

Re: [ClusterLabs] Feedback wanted: changing "master/slave" terminology

On Thu, 25 Jan 2018 15:21:30 -0500 Digimer <li...@alteeve.ca> wrote: > On 2018-01-25 01:28 PM, Ken Gaillot wrote: > > On Thu, 2018-01-25 at 13:06 -0500, Digimer wrote: > >> On 2018-01-25 11:11 AM, Ken Gaillot wrote: > >>> On Wed, 2018-01-24 at 20:5

Re: [ClusterLabs] Misunderstanding or bug in crm_simulate output

On Wed, 24 Jan 2018 17:42:56 -0600 Ken Gaillot <kgail...@redhat.com> wrote: > On Fri, 2018-01-19 at 00:37 +0100, Jehan-Guillaume de Rorthais wrote: > > On Thu, 18 Jan 2018 10:54:33 -0600 > > Ken Gaillot <kgail...@redhat.com> wrote: > > > > > On Thu,

Re: [ClusterLabs] Feedback wanted: changing "master/slave" terminology

On Thu, 25 Jan 2018 10:03:34 +0100 Ivan Devát wrote: > > I think there's enough sentiment for "promoted"/"started" as the role > > names, since it most directly reflects how pacemaker uses them. > > > Just a question. > The property "role" of a resource operation can have

Re: [ClusterLabs] Feedback wanted: changing "master/slave" terminology

On Thu, 25 Jan 2018 11:28:16 +0100 Jehan-Guillaume de Rorthais <j...@dalibo.com> wrote: > On Thu, 25 Jan 2018 10:03:34 +0100 > Ivan Devát <ide...@redhat.com> wrote: > > > > I think there's enough sentiment for "promoted"/"started" as the rol

Re: [ClusterLabs] Feedback wanted: changing "master/slave" terminology

On Fri, 26 Jan 2018 09:37:39 -0600 Ken Gaillot wrote: ... > > All RA > > must implement the first two states "stopped" and "started". The > > cases where RA > > is promotable should then be called..."promotable" I suppose. > > > > However, why exactly should we find a

Re: [ClusterLabs] Does anyone use clone instance constraints from pacemaker-next schema?

On Thu, 11 Jan 2018 12:00:25 -0600 Ken Gaillot <kgail...@redhat.com> wrote: > On Thu, 2018-01-11 at 20:11 +0300, Andrei Borzenkov wrote: > > 11.01.2018 19:21, Ken Gaillot пишет: > > > On Thu, 2018-01-11 at 01:16 +0100, Jehan-Guillaume de Rorthais > > > wrote:

Re: [ClusterLabs] Does CMAN Still Not Support Multipe CoroSync Rings?

r: https://clusterlabs.github.io/PAF/Quick_Start-CentOS-6.html#cluster-creation Other chapter might not be useful to you. Do not hesitate to give feedback if something changed or doesn't work anymore. This was based on CentOS 6.7. Cheers, -- Jehan-Guillaume de Rortha

Re: [ClusterLabs] Clearing failed actions

On Fri, 06 Jul 2018 10:15:08 -0600 Casey Allen Shobe wrote: > Hi, > > I found a web page which suggested to clear the Failed Actions, to use > `crm_resource -P`. Although this appears to work, it's not documented on the > man page at all. Is this deprecated and is there a more correct way to

Re: [ClusterLabs] 答复: 答复: 答复: How to configure to make each slave resource has one VIP

slave-ip2 > pgsql-master-ip setoptions score=-1000 The score seems too high in my opinion, compared to other ones. You should probably remove all the colocation constraints and try with the one I pushed online. Regards, > -邮件原件- > 发件人: Jehan-Guillaume de Rorthais [mailto:j...@d

Re: [ClusterLabs] 答复: 答复: 答复: How to configure to make each slave resource has one VIP

On Fri, 9 Mar 2018 00:54:00 + 范国腾 wrote: > Thanks Rorthais, Got it. The following command could make sure that it move > to the master if there is no standby alive: > > pcs constraint colocation add pgsql-ip-stby1 with slave pgsql-ha 100 > pcs constraint colocation

Re: [ClusterLabs] 答复: 答复: 答复: How to configure to make each slave resource has one VIP

On Wed, 7 Mar 2018 01:27:16 + 范国腾 wrote: > Thank you, Rorthais, > > I read the link and it is very helpful. Did you read the draft I attached to the email? It was the main purpose of my answer: helping you with IP on slaves. It seems to me your mail is reporting

Re: [ClusterLabs] How to setup a simple master/slave cluster in two nodes without stonith resource

On Tue, 3 Apr 2018 02:07:50 + 范国腾 wrote: > Hello, > > I want to setup a cluster in two nodes. One is master and the other is slave. > I don’t need the fencing device because my internal network is stable. How much stable it is? This assumption is frequently wrong.

Re: [ClusterLabs] Cluster fails to start on rebooted nodes without manual fiddling...

On Mon, 02 Apr 2018 14:05:09 -0600 Casey & Gina wrote: [...] > Now, if I restart the second node, and execute `pcs cluster start` once it's > back up, it fails to start the resource and shows me this in the `pcs status` > output: > > > -- > *

Re: [ClusterLabs] How to setup a simple master/slave cluster in two nodes without stonith resource

On Tue, 3 Apr 2018 14:41:56 +0200 Jehan-Guillaume de Rorthais <j...@dalibo.com> wrote: > On Tue, 3 Apr 2018 02:07:50 + > 范国腾 <fanguot...@highgo.com> wrote: > > > Hello, > > > > I want to setup a cluster in two nodes. One is master and the other is >

Re: [ClusterLabs] Possible idea for 2.0.0: renaming the Pacemaker daemons

On Tue, 3 Apr 2018 09:58:50 +1000 Andrew Beekhof <abeek...@redhat.com> wrote: > On Fri, Mar 30, 2018 at 8:36 PM, Jehan-Guillaume de Rorthais < > j...@dalibo.com> wrote: > > On Thu, 29 Mar 2018 09:32:41 +1100 > > Andrew Beekhof <abeek...@redhat.com> wrote: &

Re: [ClusterLabs] How to cancel a fencing request?

On Tue, 10 Apr 2018 11:24:04 +0200 Klaus Wenninger <kwenn...@redhat.com> wrote: > On 04/10/2018 08:48 AM, Jehan-Guillaume de Rorthais wrote: > > On Mon, 09 Apr 2018 17:59:26 -0500 > > Ken Gaillot <kgail...@redhat.com> wrote: > > > >> On Tue, 201

  1   2   3   >