g Ken?).
Higher-level tools like pcs or crm shell could probably do it when
removing the resource (i.e. if the resource was a promotable clone,
check for and remove any node attributes of the form master-$RSC_ID).
That sounds like a good idea to me.
Pacemaker would be a bad place to do it becau
and crm_mon will be added with the next
release.
In the meantime, most people just execute the command-line tools
directly from their code.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
On Fri, 2022-03-04 at 08:17 +0100, Ulrich Windl wrote:
> > > > Ken Gaillot schrieb am 02.03.2022 um
> > > > 16:10 in
> Nachricht
> :
> > On Wed, 2022-03-02 at 08:41 +0100, Ulrich Windl wrote:
> > > > > > Ken Gaillot schrieb
On Wed, 2022-03-02 at 08:41 +0100, Ulrich Windl wrote:
> > > > Ken Gaillot schrieb am 01.03.2022 um
> > > > 16:04 in
> Nachricht
> <463458e414f7c411eb1107335be6ee9a6e2d13ee.ca...@redhat.com>:
> > On Tue, 2022‑03‑01 at 10:05 +0100, Ulrich Windl wrote:
>
;
> (pacemaker-2.0.5+20201202.ba59be712-150300.4.16.1.x86_64)
>
> Did I misunderstand something, or does it look like a bug?
>
> Regards,
> Ulrich
>
>
> ___
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users
>
> ClusterLabs home: https://www.clusterlabs.org/
>
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
tarting the stop of the other
> resources.
> Cluster tried to "abort" the shutdown, but shutdown can't be aborted.
> And i had bad luck that the shutdown of this domain took so long.
>
> Correct ?
>
> Bernd
>
Yes, other than the cluster isn't trying to abort the shutdown, it's
just discarding any actions that were planned after it in the same
transition.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
ew actions from the transition -- but any actions
currently in flight must complete before the new transition can be
calculated.
Changes that abort a transition include configuration changes, a node
joining or leaving, an unexpected action result being received, a node
attribute changing, the cluster-r
s "complete=false"
> ?
> What does that mean ?
>
> Bernd
"Complete" is whether all actions originally planned in the transition
were completed. For complete=true, the log is basically just a heads-up
that the cluster needs to recheck things, since there's nothing to
actually abort.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
le transitions. Often when some event
is happening, lots of micro-conditions (action results, node attribute
changes, etc.) change in a short time, and you'll see a new transition
after each one.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
kernel.
> But still, when booting correctly, the cluster would still try to
> "recover" from the false "is active on 2 nodes", so the true fix was
> a manual "cleanup" of the migration entries.
>
> Pacemaker &qu
nstead. Plus maybe replace "aborted" with "interrupted",
so then we'd have "Action plan interrupted" which is maybe a little
more understandable.
>
> Transition 128 is finished:
> Feb 15 21:04:26 [15370] ha-idg-2 crmd: notice:
> run_graph: Transition 128 (Complete=1, Pending=0, Fired=0,
> Skipped=0, Incomplete=0, Source=/var/lib/pacemaker/pengine/pe-input-
> 3548.bz2): Complete
>
> And one second later the shutdown starts. Is that normal that there
> is such a big time gap ?
>
> Bernd
No, there should be another transition calculated (with a "saving
input" message) immediately after the original transition is aborted.
What's the timestamp on that?
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
utilization counting "static" resource consumption, one
> could have a
> dynamic resource consumption (counting semaphore-like) that is
> consumed while
> an operation on an instance naming that resource is being performed.
> So when you name your resource "concurrent_vm_ops" and asign that to
> every vm
> configuration, eventually initalizing the resource to siome thing
> like 2 or 3,
> then you could limit the concurrent VM invocations. Likewise, for
> less heave
> instances you could use more relaxed settings or no restrictions at
> all...
>
> Regards,
> Ulrich
>
You can accomplish something similar with an ordering constraint with
kind=Serialize. In the case of "start vm1 then start vm2" with
kind=Serialize, it means that vm1 and vm2 will not be started
simultaneously, but neither actually requires the other or has to be
done in a specific order.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
to execute the Pacemaker command-line tools to do
what you want.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
but hopefully
> it
> at least clarified a bit what's going on.
>
>
> Regards,
> Tomas
>
>
> Dne 29. 01. 22 v 6:12 Digimer napsal(a):
> > On 2022-01-29 00:10, Digimer wrote:
> > > On 2022-01-28 16:54, Ken Gaillot wrote:
> > >
, which includes the is-managed setting,
Pacemaker no longer knows the resource is unmanaged. And even if you
set it via resource defaults or something, eventually you have to set
it back, at which point Pacemaker will still have the same response.
--
Ken Gaillot
_
vance.
I'd check for SELinux denials first. A command executed from the
command line is unconstrained, while being executed by a daemon is
subject to SELinux policies.
Other than that, maybe turn on any debugging options and check the
keycloak logs from the container (e.g. using network logging or an
e
al English, and the "msgstr" entries
are the translations. You can either review them in github or reply
here.
Thanks to anyone who can help!
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
Clu
> both Resource Groups to improve the failover time?
>
> BR,
> J. Gogu
The only thing I can think of is on-fail=fence
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
slated, when a more complex setup is
> needed -> you will always have to search in the source/github
> issues/documentation/mailing list history and rely on English.
>
> Best Regards,
> Strahil Nikolov
>
> > On Tue, Jan 11, 2022 at 9:23, Ulrich Windl
> >
Re-raising this due to the recent holidays ...
Is translation of Pacemaker option help and man pages something people
would like to see?
Would anyone be willing to contribute or proofread translations if the
tools were easy?
On Fri, 2021-12-03 at 15:02 -0600, Ken Gaillot wrote:
> Hi
is back online 100%.
> >
> > Fabio
> > ___
> > Manage your subscription:
> > https://lists.clusterlabs.org/mailman/listinfo/developers
> >
> > ClusterLabs home: https://www.clusterlabs.org/
>
monitor interval=30s
> (c8kubermaster1-monitor-interval-30s)
>start interval=0s timeout=60s
> (c8kubermaster1-start-interval-0s)
>stop interval=0s timeout=60s
> (c8kubermaster1-stop-interval-0s)
>
> Any and all suggestions & thoughts
On Sat, 2021-12-11 at 13:49 +, lejeczek via Users wrote:
>
> On 10/12/2021 21:17, Ken Gaillot wrote:
> > On Fri, 2021-12-10 at 16:33 +, lejeczek via Users wrote:
> > > Hi guys.
> > >
> > > I quite often.. well, to frequently in my mind, see a VM
&
the master branch as a patch.
Since this only affects the display, there are no plans for a special
release. The fix will land in the next normal release, expected around
the middle of 2022.
--
Ken Gaillot
___
Manage your subscription:
https
>migrate_to interval=0s timeout=180s
> (c8kubermaster2-migrate_to-interval-0s)
>monitor interval=30s
> (c8kubermaster2-monitor-interval-30s)
>start interval=0s timeout=90s
> (c8kubermaster2-start-interval-0s)
>
-Ei 'pcs|pacemaker|corosync'
> pacemaker-2.0.2-2.el7.x86_64
> corosync-2.4.4-2.el7.x86_64
> pcs-0.9.169-1.el7.x86_64
> [root@node01 testadmin]#
>
> Thanks and Regards,
> S Sathish S
--
Ken Gaillot
___
Manage your subscription:
http
ace for translations, but with this
initial proof-of-concept, it involves github pull requests and reviews.
Thoughts?
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
due to internal cluster issues as opposed to agent
issues. As usual, it also includes a number of bug fixes.
Many thanks to all contributors of source code to this release,
including Chris Lumens, Ferenc Wágner, Gao,Yan, Grace Chin, Hideo
Yamauchi, Ken Gaillot, Klaus Wenninger, and Oyvind
upgrade past 1.1.15 would put you in
the same situation -- if the 1.1.15 node leaves the cluster, it can't
rejoin until it's upgraded to the newer version.
> Thank you very much for your help!
> _Vitaly
>
> > On November 23, 2021 5:12 PM Ken Gaillot
> > wrote:
> >
seen at:
https://wiki.clusterlabs.org/wiki/ReleaseCalendar
1.1.13 through 1.1.15 had feature set 3.0.10
> 3. Where could I get source rpms to rebuild this rpm on CentOs 8?
> Thanks a lot!
> _Vitaly Zolotusky
The stock packages in the repos should be fine. All new
ain the intermittence I
> > > saw
> > > this
> > > morning. If I set that to 1 minute would that cause any gross
> > > negative
> > > issues?
> >
> > It increases CPU usage and IPC traffic. For Pacemaker 2.0.3 or
> > later,
to 1 minute would that cause any gross
> negative
> issues?
It increases CPU usage and IPC traffic. For Pacemaker 2.0.3 or later, I
definitely wouldn't bother. For older versions, 1 minute feels a bit
much, I would go with around 5.
>
> Is there another setting besides cluster-recheck-
contributors of source code to this release,
including Chris Lumens, Ferenc Wágner, and Ken Gaillot.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
se. Any help is appreciated!
>
> Thanks.
Failure handling is configurable via the on-fail meta-attribute. You
can set on-fail=fence for the ethmonitor resource's monitor action to
fence the node if the monitor fails. There's also on-fail=standby, but
that will still try to stop any
On Fri, 2021-11-05 at 11:22 +0300, Andrei Borzenkov wrote:
> On 05.11.2021 01:20, Ken Gaillot wrote:
> > > There are two issues discussed in this thread.
> > >
> > > 1. Remote node is fenced when connection with this node is lost.
> > > For
> > > al
two resource start and
> stop in a particular order, but also define that if one has to be
> started or stopped the other must as well (in my defined order).
>
> Thanks.
>
> Greg Neitzert | Lead Software Engineer | RTC Software Engineering 2B
> - Middleware
> Unisys Cor
On Sat, 2021-10-30 at 21:17 +0300, Andrei Borzenkov wrote:
> On 29.10.2021 18:37, Ken Gaillot wrote:
> ...
> > > > > To address the original question, this is the log sequence I
> > > > > find
> > > > > most
> > > > > relevant:
>
nc somewhere.
I'm not aware of what might cause that. I'd check the corosync logs for
clues.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
Gaillot, Klaus Wenninger, and Oyvind Albrigtsen.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
On Fri, 2021-10-29 at 18:18 +0300, Andrei Borzenkov wrote:
> On 29.10.2021 18:16, Andrei Borzenkov wrote:
> > On 29.10.2021 17:53, Ken Gaillot wrote:
> > > On Fri, 2021-10-29 at 13:59 +, Gerry R Sommerville wrote:
> > > > Hey Andrei,
> > > >
On Fri, 2021-10-29 at 08:24 +0200, Ulrich Windl wrote:
> > > > Ken Gaillot schrieb am 28.10.2021 um
> > > > 17:28 in
> Nachricht
> :
> > Hi all,
> >
> > I hope to release the first release candidate for Pacemaker 2.1.2
> > next
e fenced. There was
nowhere to recover the connection. I'd need to see the CIB from that
time to know why; it's possible you had an old constraint banning the
connection from the other node (e.g. from a ban or move command), or
something like that.
--
Ken Gaillot
_
pointer in the right direction).
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
t), but I don't think they're worth staying on 2.
> Thanks,
>
> Toby Haynes
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
On Wed, 2021-10-20 at 09:35 +0200, Ulrich Windl wrote:
> > > > Ken Gaillot schrieb am 19.10.2021 um
> > > > 19:16 in
> Nachricht
> :
> > Hi all,
> >
> > I hope to get the first release candidate for Pacemaker 2.1.2 out
> > in a
> >
ueued=0ms,
> exec=0ms
>
> Now, the exit reason will plainly say what happened:
>
> * rsc1_monitor_6 on node1 'error' (1): call=188, status='Error',
> exitreason='Process interrupted by signal', last-rc-change='Fri Sep
> 24
> 14:45:02 2021', queued=0ms, exec=0ms
>
queued=0ms, exec=0ms
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
ny group or constraints.
> The same is true with colocation statements - if a constraint is made
> with a ping resource without using a rule that references pingd then
> the dampen behaviour is ignored completely.
>
> Is the ping'er missing something that does this:
>
> score
ction.
It's in the Developers section, which makes no sense really. I'll
cross-link it from Documentation when I get the chance ...
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
How can I configure the cluster so that remote node srv-4 fails over
> instead of getting fenced?
>
>
> Thank you
>
> Janghyuk Boo.
Hi,
That is how it works whenever possible. If it fences the remote, it is
because it was not recoverable. Logs from srv-1, srv-2, and srv-4
around that time would be helpful to give more detail.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
ejoining),
the CIB versions will be compared, and the newest one wins (actually
more like the one with the most changes).
Generally, the existing cluster had more activity after the node was
fenced, and the fenced node has little to no activity before it rejoins
the cluster, so it works out well. However
On Fri, 2021-10-08 at 08:18 +0200, Ulrich Windl wrote:
> > > > Ken Gaillot schrieb am 07.10.2021 um
> > > > 22:53 in
> Nachricht
> <8bec6dc04c52d4ac5c2a8055eb7bae455f5a449d.ca...@redhat.com>:
> > Hi all,
> >
> > We're looking ahead to the
w supports backslash-escaped
characters (such as spaces) in the mapped name. For example, you could
set pcmk_host_map="node1:Plug\ 1;node2:Plug\ 2" if the device expects
"Plug 1" and "Plug 2" as the names.
--
Ken Gaillot
_
got those
> right.)
>
> I suppose another way to go about this would be to run another
> clone'd resource that mimics the ping and automatically runs a
> "resource cleanup MyGw-clone" if it notices the clone is down on and
> node and the ping would succeed. But is there a cleaner way?
>
> Thanks,
> D.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
abases are stopped?
>
> Best Regards,
> John
Hi,
Yes, make the colocation optional (i.e. use a finite integer score)
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
corosync traffic should go over (cluster token passing and control
messages). Often this is a dedicated network so cluster traffic can't
be crowded out by a networking spike (which might otherwise lead to
fencing).
--
Ken Gaillot
___
Manage your
t for an operation that does already
have an explicit timeout, you'll have to use "pcs cluster edit" or
cibadmin with the raw XML.
> > On Mon, Sep 27, 2021 at 19:56, Ken Gaillot
> > wrote:
> > On Mon, 2021-09-27 at 12:37 +0200, Lentes, Bernd wrote:
> > > Hi,
>
ce mode for the window, or
disable the monitor for the window. Of course that also disables any
cluster response. You could instead lengthen operation timeouts during
the window.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
On Sat, 2021-09-18 at 08:29 +0300, Andrei Borzenkov wrote:
> On 17.09.2021 22:13, Ken Gaillot wrote:
> > On Fri, 2021-09-17 at 15:54 +0200, Lentes, Bernd wrote:
> > > Hi,
> > >
> > > today i configured tracing for some VirtualDomains:
> > >
> >
; > It
> > would be nice to come up with a general solution that all agents
> > can
> > use rather than modify each agent's meta-data individually, but
> > either
> > approach would work.
>
> Bernd
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
configuration change that requires a restart. With the new
> > OCF
> > 1.1 standard, the trace parameter could be marked reloadable, but
> > the
> > agents need to be updated to do that.
> > --
> > Ken Gaillot
>
> Hi Ken,
>
> but does pacemaker do it
thanks to all contributors of source code to this release,
including Chris Lumens, Christine Caulfield, Emil Penchev, Gao,Yan,
Grace Chin, Hideo Yamauchi, José Guilherme Vanz, Ken Gaillot, Klaus
Wenninger, and Oyvind Albrigtsen.
--
Ken Gaillot
___
Manage
1 to other network segments, the same test cluster can
> switch normally.
Does the systemd journal or /var/log/pacemaker/pacemaker.log show any
interesting messages around the time of the test?
>
> ------ 原始邮件 --
> 发件人: "Ken Gaillot" ;
> 发送时间: 2021
figure a recurring monitor on the IP resource? Without a
monitor, the cluster will only start the resource.
> journalctl will tell you a lot of cluster messages and might tell you
> the
> reason behind.
>
> [1] https://access.redhat.com/solutions/30564
>
> Cheers,
> Roger
&g
-2.1.1-rc3
For details, see the ChangeLog in the source repository. Everyone is
encouraged to download, compile and test the new release. We do many
regression tests and simulations, but we can't cover all possible use
cases, so your feedback is important and appreciated.
--
Ken Gaillot
ulations, but we can't cover all
possible use cases, so your feedback is important and appreciated.
Many thanks to all contributors of source code to this release,
including Aleksei Burlakov, Chris Lumens, Christine Caulfield, Gao,Yan,
Grace Chin, Hideo Yamauchi, Jan Pokorný, Kazunori INOUE, Ke
atthew, can you give more details about your use case?
If you only need one NFS server, then it's fine not to clone it. The
groups can be ordered after the NFS server without requiring them to be
colocated with it.
> > On Fri, Apr 30, 2021 at 18:44, Matthew Schumacher
> > wrote:
> >
On Fri, 2021-04-30 at 19:24 +0300, Andrei Borzenkov wrote:
> On 30.04.2021 17:57, Ken Gaillot wrote:
> > On Fri, 2021-04-30 at 11:00 +0100, lejeczek wrote:
> > > Hi guys
> > >
> > > I'd like to ask around for thoughts & suggestions on any
> >
t
only makes sense if restarting whatever resource is listed as the
container can make the dependent resource OK again.
>
> > On Fri, Apr 30, 2021 at 17:57, Ken Gaillot
> > wrote:
> > On Fri, 2021-04-30 at 11:00 +0100, lejeczek wrote:
> > > Hi guys
> > >
t; ___________
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users
>
> ClusterLabs home: https://www.clusterlabs.org/
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
ce being monitored is inside a VirtualDomain, named vm1 for
example, you can configure the nagios resource with the resource meta-
attribute container="vm1". If the nagios check fails, Pacemaker will
restart vm1.
(This feature was added before OS containers became popular, so the
naming
On Thu, 2021-04-29 at 09:14 +0200, Ulrich Windl wrote:
> > > > Ken Gaillot schrieb am 28.04.2021 um
> > > > 19:00 in
>
> Nachricht
> :
> > On Wed, 2021‑04‑28 at 18:14 +0200, Jehan‑Guillaume de Rorthais
> > wrote:
> > > Hi all,
> > >
On Wed, 2021-04-28 at 19:19 +0200, Jehan-Guillaume de Rorthais wrote:
> On Wed, 28 Apr 2021 12:00:40 -0500
> Ken Gaillot wrote:
>
> > On Wed, 2021-04-28 at 18:14 +0200, Jehan-Guillaume de Rorthais
> > wrote:
> > > Hi all,
> > >
> > > It seem
tire node_state XML
subtree; you can add -n/--no-children to return just the node_state
element itself.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
ceaa3a-
> 3.3.1.21516.1.PTF.1182607.x86_64
> resource-agents-4.4.0+git57.70549516-3.12.1.x86_64
>
> Regards,
> Ulrich
>
>
>
> ___
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users
>
> ClusterLabs home: https://www.cluster
know it's the last node and shut down without
> complaint?
It knows, it's just not sure you know :)
pcs's design philosophy is to hand-hold users by default and give
expert users --force.
The idea in this case is that (especially in 3-to-5-node clusters)
someone migh
at the
problem.
The automated approach leans more to quick self-recovery, and is more
convenient in larger organizations where not every administrator that
has access to the host for applying updates etc. is trained on the
cluster software.
--
Ken Gaillot
__
g is an optional ordering. If A is ordered
after B optionally, and both have to move, A will stop, then B will
stop, then B will start, then A will start. If only B has to move, it
won't force A to restart.
--
Ken Gaillot
___
Manage your subscription
ens. Apparently negative score completely prevents assigning
> > resource to this node, and "should" here probably means "it is
> still
> > possible that final score may become positive".
> >
> > As it is not possible to refer to attributes of multiple nodes in a
> > rule, you would need something that combines current pingd status
> for
> > individual nodes and makes it available. Logical place is
> > ocf:pacemaker:ping resource agent itself.
> ___
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users
>
> ClusterLabs home: https://www.clusterlabs.org/
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
, and "should" here probably means "it is still
> possible that final score may become positive".
>
> As it is not possible to refer to attributes of multiple nodes in a
> rule, you would need something that combines current pingd status for
> individual nodes and makes it available. Logical place is
> ocf:pacemaker:ping resource agent itself.
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
set the
configured default via a rsc_defaults entry in new CIBs, so that it
won't affect existing clusters or rolling upgrades (current users won't
see behavior change), and unlike implicit defaults, users can query and
remove resource defaults.
--
Ken Gaillot
er version of post_join_delay?
> > B) is there a compelling argument NOT to use post_join_delay
> > behaviour
> > in pacemaker I am not seeing?
> >
> > Thanks!
> >
>
> ___
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users
>
> ClusterLabs home: https://www.clusterlabs.org/
>
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
ml has continued to use --as-xml, but will switch to
--output-as=xml, thus Tomas's warning.
> I will try to start with "pcs status xml" in the future.
>
> Regards,
> tbskyd
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
tch but,
> naturally the obvious question would be - why that is even
> allowed to happen?
> many thanks, L.
> ___
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users
>
> ClusterLabs home: https://www.clusterlabs.org/
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
name="clone-max" value="2"/>
>
> name="master-max" value="1"/>
>
> name="notify" value="true"/>
>
use the same cluster management commands they're
familiar with, and certain resources can always run at the DR site to
keep it ready (e.g. shared storage or a database replicant).
There are some ideas about making such a setup easier to manage, such
as being able
prefer a particular node, you can use
location constraints to express that. However there is rarely a need to
do so; in most clusters, nodes are equally interchangeable.
>
> On Thursday, April 8, 2021, 06:49:38 PM GMT+4:30, Ken Gaillot <
> kgail...@redhat.com> wrote:
>
>
&g
he above status output, the web server is running on node2,
using the IP address specified by the httpd_vip resource. Are you
trying to contact the web server at a name corresponding to that IP?
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
On Tue, 2021-04-06 at 09:15 +0200, Ulrich Windl wrote:
> > > > Ken Gaillot schrieb am 31.03.2021 um
> > > > 15:48 in
>
> Nachricht
> <7dfc7c46442db17d9645854081f1269261518f84.ca...@redhat.com>:
> > On Wed, 2021‑03‑31 at 14:32 +0200, Antony S
it, but it
> couldn't start!
> How to solve it?
>
> Thanks.
> ___
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users
>
> ClusterLabs home: https://www.clusterlabs.org/
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
interactions) and
> the fail-count does not go away.
>
>
> Does anyone have suggestions on how to debug this difference in
> behaviour
> between pacemaker 1.1.16 and 2.0.1, because at present it prevents me
> being
> able to upgrade an operational cluster, as the
gt; seconds ago"?
Unfortunately, there is no way. failure-timeout expires *all* failures
once the *most recent* is that old. It's a bit counter-intuitive but
currently, Pacemaker only remembers a resource's most recent failure
and the total count of failures, and changing that would be a big
project.
> Thanks,
>
>
> Antony.
>
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
On Tue, 2021-03-30 at 08:01 +0300, Andrei Borzenkov wrote:
> On 29.03.2021 20:12, Ken Gaillot wrote:
> > On Sun, 2021-03-28 at 09:20 +0300, Andrei Borzenkov wrote:
> > > On 28.03.2021 07:16, Strahil Nikolov wrote:
> > > > I didn't mean DC as a designated
On Tue, 2021-03-30 at 08:26 +0200, Ulrich Windl wrote:
> > > > Ken Gaillot schrieb am 29.03.2021 um
> > > > 19:23 in
>
> Nachricht
> :
> > Scores are in the range ‑1,000,000 to +1,000,000 (also known as
> > "infinity").
> >
> &
re="INFINITY" with-rsc-
> > role="Master" node-attribute="hana__site"/>
> >
> > On Mon, Mar 29, 2021 at 9:07 PM Strahil Nikolov <
> > hunter86...@yahoo.com> wrote:
> > > Hi Ken, can you provide a prototype code example.
> &g
_
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users
>
> ClusterLabs home: https://www.clusterlabs.org/
>
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
anks for help!
> > > > ___
> > > > Manage your subscription:
> > > > https://lists.clusterlabs.org/mailman/listinfo/users
> > > >
> > > > ClusterLabs home: https://www.clusterlabs.org/
> > &g
e essentially duplicating your RA
> > functionality because you will somehow need to find out which site
> > is
> > currently primary.
> >
> > There is no guarantee that pacemaker DC wil be on the same site as
> > SAP
> > HANA primary system.
> >
> >
>
> ___
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users
>
> ClusterLabs home: https://www.clusterlabs.org/
>
--
Ken Gaillot
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
I've made a note of these as ideas for 1.2/2.0 :)
On Sun, 2021-03-28 at 03:03 +0200, Ulrich Windl wrote:
> On 3/26/21 11:17 PM, Ken Gaillot wrote:
> > OCF 1.1 is now formally adopted!
> >
> > https://github.com/ClusterLabs/OCF-spec/blob/master/ra/1.1/resource-agent-a
OCF 1.1 is now formally adopted!
https://github.com/ClusterLabs/OCF-spec/blob/master/ra/1.1/resource-agent-api.md
Thanks to everyone who gave feedback.
Now to add support for it ...
On Tue, 2021-03-09 at 17:07 -0600, Ken Gaillot wrote:
> Hi all,
>
> After many false starts over the
201 - 300 of 1689 matches
Mail list logo
