[ClusterLabs] redis and pgsql RAs under pacemaker_remote does not work

Hi! I'm running redis and PostgreSQL in LXC containers with pacemaker_remote on hosts running full cluster stack. In pacemaker_remote installation crm_attribute utility is absent, so subj RAs are not working. May be crm_resource can be used for the same purpose, storing state data in resource

[ClusterLabs] 答复: 答复: pacemaker reports monitor timeout while CPU is high

Thank you very much, Ken. I will set the high timeout and try. -邮件原件- 发件人: Ken Gaillot [mailto:kgail...@redhat.com] 发送时间: 2018年1月11日 23:48 收件人: Cluster Labs - All topics related to open-source clustering welcomed 抄送: 王亮 主题: Re:

[ClusterLabs] pengine bug? Recovery after monitor failure: Restart of DRBD does not restart Filesystem -- unless explicit order start before promote on DRBD

To understand some weird behavior we observed, I dumbed down a production config to three dummy resources, while keeping some descriptive resource ids (ip, drbd, fs). For some reason, the constraints are: stuff, more stuff, IP -> DRBD -> FS -> other stuff. (In the actual real-world config, it

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

On Thu, 11 Jan 2018 12:00:25 -0600 Ken Gaillot 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: > > > > On Wed, 10 Jan 2018

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

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: > > > On Wed, 10 Jan 2018 12:23:59 -0600 > > > Ken Gaillot wrote: > > > ... > > > > My question is:

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

11.01.2018 19:21, Ken Gaillot пишет: > On Thu, 2018-01-11 at 01:16 +0100, Jehan-Guillaume de Rorthais wrote: >> 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

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

On Thu, 2018-01-11 at 08:54 +0100, Ulrich Windl wrote: > On "--crm_xml -> --xml-text": Why not simply "--xml" (XML IS text)? Most Pacemaker tools that accept XML can get it from standard input ( --xml-pipe), a file (--xml-file), or a literal string (--xml-text). Although, looking at it now, it

Re: [ClusterLabs] Changes coming in Pacemaker 2.0.0

On Thu, 2018-01-11 at 01:21 +0100, Jehan-Guillaume de Rorthais wrote: > 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 > >

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

On Thu, 2018-01-11 at 01:16 +0100, Jehan-Guillaume de Rorthais wrote: > 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

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

Jehan-Guillaume de Rorthais writes: > > For what is worth, while using crmsh, I always have to explain to > people or customers that: > > * we should issue an "unmigrate" to remove the constraint as soon as the > resource can get back to the original node or get off the

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] 答复: pacemaker reports monitor timeout while CPU is high

On Thu, 2018-01-11 at 03:50 +, 范国腾 wrote: > Thank you, Ken. > > We have set the timeout to be 10 seconds, but it reports timeout only > after 2 seconds. So it seems not work if I set higher timeouts. > Our application which is managed by pacemaker will start more than > 500 process to run

Re: [ClusterLabs] Antw: Re: Coming in Pacemaker 2.0.0: /var/log/pacemaker/pacemaker.log

On Thu, 2018-01-11 at 09:10 +0100, Ulrich Windl wrote: > Maybe the question to ask right now would be: What are the modules, > and what are their logfile locations? An opportunity to clean up the > mess! It would be nice, but time is always constrained, and coordinating multiple projects takes

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

On Thu, Jan 11, 2018 at 2:52 PM, Ulrich Windl wrote: > > Andrei Borzenkov schrieb am 11.01.2018 um 12:41 in > Nachricht > : >> On Thu, Jan 11, 2018 at 10:54 AM, Ulrich

Re: [ClusterLabs] Antw: Coming in Pacemaker 2.0.0: Reliable exit codes

On Thu, 2018-01-11 at 08:59 +0100, Ulrich Windl wrote: > Hi! > > Will those exit code be compatible with , i.e. will it be > a superset or a subset of it? If not, it would be the right time. Yes! It will be a superset. From the new source code: /*  * Exit statuses  *  * We want well-specified

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

On Thu, 2018-01-11 at 12:52 +0100, Ulrich Windl wrote: > > > > Andrei Borzenkov schrieb am 11.01.2018 um > > > > 12:41 in > > Nachricht > : > > On Thu, Jan 11, 2018 at 10:54 AM, Ulrich Windl > >

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

On Thu, 2018-01-11 at 09:12 +0100, Ulrich Windl wrote: > BTW: Could be fix that "Master/slave resources need different > monitoring intervals for master and slave" at this time? Unfortunately that would be a major project, as the interval is used to identify the operation throughout the code

Re: [ClusterLabs] Recommendations for securing DLM traffic?

- Original Message - | What are the general recommendations for securing traffic for DLM on port | 21064? | | It appears that this traffic is not signed or encrypted in any way so whilst | there might not be any privacy issues with information disclosure it's not | clear that the messages

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

>>> Andrei Borzenkov schrieb am 11.01.2018 um 12:41 in Nachricht : > On Thu, Jan 11, 2018 at 10:54 AM, Ulrich Windl > wrote: >> Hi! >> >> On the tool changes, I'd prefer

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

On Thu, Jan 11, 2018 at 10:54 AM, Ulrich Windl wrote: > Hi! > > On the tool changes, I'd prefer --move and --un-move as pair over --move and > --clear ("clear" is less expressive IMHO). --un-move is really wrong semantically. You do not "unmove" resource - you

[ClusterLabs] Recommendations for securing DLM traffic?

What are the general recommendations for securing traffic for DLM on port 21064? It appears that this traffic is not signed or encrypted in any way so whilst there might not be any privacy issues with information disclosure it's not clear that the messages could not be replayed or otherwise

[ClusterLabs] Antw: 答复: Antw: pacemaker reports monitor timeout while CPU is high

Hi! A few years ago I was playing with cgroups, getting quite interesting (useful) results, but applying the cgroups to existing and newly started processes was quite hard to integrate into the OS, so I did not proceed on that way. I think cgroups is even more powerful today, but I haven't

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

BTW: Could be fix that "Master/slave resources need different monitoring intervals for master and slave" at this time? >>> Jehan-Guillaume de Rorthais schrieb am 11.01.2018 um >>> 01:16 in Nachricht <20180111011616.496a383b@firost>: > On Wed, 10 Jan 2018 12:23:59 -0600 > Ken

[ClusterLabs] Antw: Re: Coming in Pacemaker 2.0.0: /var/log/pacemaker/pacemaker.log

Maybe the question to ask right now would be: What are the modules, and what are their logfile locations? An opportunity to clean up the mess! >>> Adam Spiers schrieb am 11.01.2018 um 00:59 in Nachricht <20180110235939.fvwkormbruoqhwfb@pacific.linksys.moosehall>: > Ken

[ClusterLabs] Antw: Coming in Pacemaker 2.0.0: /var/log/pacemaker/pacemaker.log

Hi! More than the location of the log file, I'm interested in the contents of the log file: The log file should have a formal syntax for automated parsing, and it should be as compact as possible. Considering lines like: Jan 07 10:07:41 [10691] h01pengine: info:

[ClusterLabs] Antw: Coming in Pacemaker 2.0.0: Reliable exit codes

Hi! Will those exit code be compatible with , i.e. will it be a superset or a subset of it? If not, it would be the right time. Regards, Ulrich >>> Ken Gaillot schrieb am 10.01.2018 um 23:22 in >>> Nachricht <1515622941.4815.21.ca...@redhat.com>: > Every time you run a