Re: [ClusterLabs] Antw: Clone resource active only if all nodes are active
On 22.01.2018 16:44, Ken Gaillot wrote: > On Mon, 2018-01-22 at 14:18 +0100, Ulrich Windl wrote: >> Did you try meta clone-node-min=3? > clone-min does not affect the clone it's configured on, but rather > anything ordered relative to it via a constraint. It's for the case > where a resource needs a certain number of instances running before > other services can consider it effective. > > It could be helpful here if the reason you want the service to stop is > to get some other resource to stop. > >> "alu...@poczta.onet.pl" schrieb am > 22.01.2018 um 13:29 >> in Nachricht <844fdf99-1680-3ed8-6afc-8b3e2ddea...@poczta.onet.pl>: >>> I need to create configuration when one resource is active on all >>> nodes >>> and is only active when all nodes are active. It should has the > There's no built-in capability for that. > > It's possible you could get something to work using clone > notifications. You could write a custom OCF agent that simply sets a > local node attribute to 0 or 1. If > OCF_RESKEY_CRM_meta_notify_inactive_resource is empty, it would set it > to 1, otherwise it would set it to 0. (You could use > ocf:pacemaker:attribute from a recent Pacemaker as a starting point.) > > Then you could use a rule to locate your desired resource where the > attribute is set to 1. > > > http://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/1.1/html-single/Pa > cemaker_Explained/index.html#_clone_resource_agent_requirements > > http://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/1.1/html-single/Pa > cemaker_Explained/index.html#idm140583511697312 It seems that idea is going to work :) Thank you for the all propositions. >>> same >>> priority on all nodes. The major target is to have my service >>> started >>> when all nodes are active and to have my service stopped in >>> "degraded" >>> state. >>> >>> I tried clone resource with different requires options but when one >>> of >>> the node is suspended resource is still active on online node. >>> >>> Is there any options to have such type of resource? >> >> ___ >> Users mailing list: Users@clusterlabs.org >> http://lists.clusterlabs.org/mailman/listinfo/users >> >> Project Home: http://www.clusterlabs.org >> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch. >> pdf >> Bugs: http://bugs.clusterlabs.org ___ Users mailing list: Users@clusterlabs.org http://lists.clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [ClusterLabs] “pcs --debug” does not work
Hi, This saved my life-- https://roidelapluie.be/blog/2015/09/16/pcs-resource-debug/ . Well, OK, a bit of an exaggeration. Nonetheless, after a lot of frustration, it helped. Kind regards, Sean On Mon, Jan 22, 2018 at 9:24 PM Klaus Wenninger wrote: > On 01/22/2018 01:06 PM, Tomas Jelinek wrote: > > Dne 22.1.2018 v 11:01 Klaus Wenninger napsal(a): > >> On 01/22/2018 10:46 AM, Tomas Jelinek wrote: > >>> Hello, > >>> > >>> the --debug option is supposed to be used as an additional option for > >>> a pcs command, for example: > >>> > >>> pcs status --debug > >>> pcs --debug resource create dummy ocf:pacemaker:Dummy > >>> > >>> It writes what a command is doing in the background - running other > >>> commands, communicating over network. > >> > >> Although the misunderstood usage (like getting > >> everything pcs is doing on a node logged to > >> a terminal) might be an interesting feature ;-) > >> > >> Or is it possible to enable this kind of logging > >> already? Maybe via pcsd? > > > > No. Currently it is possible to: > > - increase pcsd.log verbosity by setting PCSD_DEBUG=true in > > /etc/sysconfig/pcsd or /etc/default/pcsd or whatever your distro has > > - use the --debug option in pcs commands > > and that's it. > > Thanks for the info Tomas. > When I had read the initial question on the list it just occurred to > me that might be very handy in all cases where pcs is somehow > driven by scripts/daemons. > Without having had a look into the code I would e.g. guess > digimere's 'Intelligent Availability' to fall into this category. > > Regards, > Klaus > > > > > One item on our todo list is to improve logging. It is not going to > > happen anytime soon, though, as it requires significant changes in > > pcs/pcsd architecture. > > > > Regards, > > Tomas > > > >> > >> Regards, > >> Klaus > >> > >>> > >>> > >>> > >>> Regards, > >>> Tomas > >>> > >>> > >>> Dne 22.1.2018 v 09:51 范国腾 napsal(a): > Hello, > The help of "pcs --debug" says " Print all network traffic and > external commands run." But when I run the "pcs --debug", it still > print the help information. How to trigger it to print the network > traffic? > > Thanks > Steven > > [root@db3 ~]# pcs --debug > > Usage: pcs [-f file] [-h] [commands]... > Control and configure pacemaker and corosync. > > Options: > -h, --help Display usage and exit. > -f filePerform actions on file instead of active > CIB. > --debugPrint all network traffic and external > commands run. > --version Print pcs version information. > --request-timeout Timeout for each outgoing request to another > node in > seconds. Default is 60s. > > Commands: > cluster Configure cluster options and nodes. > resourceManage cluster resources. > stonith Manage fence devices. > constraint Manage resource constraints. > propertyManage pacemaker properties. > acl Manage pacemaker access control lists. > qdevice Manage quorum device provider on the local host. > quorum Manage cluster quorum settings. > booth Manage booth (cluster ticket manager). > status View cluster status. > config View and manage cluster configuration. > pcsdManage pcs daemon. > nodeManage cluster nodes. > alert Manage pacemaker alerts. > > ___ > Users mailing list: Users@clusterlabs.org > http://lists.clusterlabs.org/mailman/listinfo/users > > Project Home: http://www.clusterlabs.org > Getting started: > http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org > > >>> > >>> ___ > >>> Users mailing list: Users@clusterlabs.org > >>> http://lists.clusterlabs.org/mailman/listinfo/users > >>> > >>> Project Home: http://www.clusterlabs.org > >>> Getting started: > >>> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > >>> Bugs: http://bugs.clusterlabs.org > >> > >> > >> > >> ___ > >> Users mailing list: Users@clusterlabs.org > >> http://lists.clusterlabs.org/mailman/listinfo/users > >> > >> Project Home: http://www.clusterlabs.org > >> Getting started: > http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > >> Bugs: http://bugs.clusterlabs.org > >> > > > > ___ > > Users mailing list: Users@clusterlabs.org > > http://lists.clusterlabs.org/mailman/listinfo/users > > > > Project Home: http://www.clusterlabs.org > > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > > Bugs: http://bugs.clusterlabs.
[ClusterLabs] pcs gui very very slow
Hello I'm new to using Pacemaker and pcsd. Is there something I'm doing wrong such that the web gui takes an extremely long time to load or do anything, like a minuet to get the initial page up. Any assistance would be greatly appreciated Ramon ___ Users mailing list: Users@clusterlabs.org http://lists.clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
[ClusterLabs] Antw: pcs gui very very slow
Hi! Is it repeatable, or just for the first start? Also how many resources do you have (roghly: dozends, hundreds, thousands,...)? And maybe tell us waht the "web GUI" qactually is. ;-) Regards, Ulrich >>> Ramon Brooker schrieb am 23.01.2018 um 19:48 in Nachricht : > Hello I'm new to using Pacemaker and pcsd. > > Is there something I'm doing wrong such that the web gui takes an extremely > long time to load or do anything, like a minuet to get the initial page up. > > Any assistance would be greatly appreciated > > Ramon ___ Users mailing list: Users@clusterlabs.org http://lists.clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
[ClusterLabs] FYI: Performance impact of recent fixes for Intel CPUs (SLES11 SP4)
Hi!
After some recent changes that also included installing the fixes for Intel CPU
defects, I've noticed some disk performance degradation (SLES11 SP4).
Unfortunately there were too many changes done to isolate the effect of the
software patches.
Yesterday I just installed the recent fixes, and the effect of performance
degradation is visible. Most interestingly it's the fastest I/O that suffers
most ("emin").
Attached is an image showing minimum, maximum and average read access time to a
FC-SAN storage system before and after the updates. The whole maintenance was
done in about six steps lasting from 14:20 to about 16:00 (marked with a yellow
box).
Notes: min and max are exponentially decaying; otherwise these values would be
quite boring.
If you look closely, you'll see that the average suffered a bit also.
There was no microcode update for the CPU (Xeon 5650 stepping 2) yet.
Docs stated that performance degradation would be visibly with SSDs mostly.
Maybe it's because the I/O delays are very low there, too.
Regards,
Ulrich
___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
