[ClusterLabs] Resources start serial, not parralel
Hello, could you help please with issue on my environment RHEL 6.6 corosync-1.4.7 pacemaker-1.1.12 When I start several resources in the same time by " pcs resource enable " command, resource doesn't start parralel, they start serial. If I start resources by one, thay start parralel. I didn't do any special settings. Please, which parameters can affect to this behavior of cluster? ___ Users mailing list: Users@clusterlabs.org http://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] Resources start serial, not parralel
There are errors in my /var/log/messages grep -e crmd\\[ -e crmd: /var/log/messages Dec 13 00:01:09 server_name_1 crmd[9941]: notice: throttle_handle_load: High CPU load detected: 3.29 Dec 13 00:01:39 server_name_1 crmd[9941]: notice: throttle_handle_load: High CPU load detected: 4.43 Dec 13 00:02:09 server_name_1 crmd[9941]: notice: throttle_handle_load: High CPU load detected: 3.90 Dec 13 00:02:39 server_name_1 crmd[9941]: notice: throttle_handle_load: High CPU load detected: 3.81 Dec 13 00:04:25 server_name_1 crmd[9941]: notice: do_state_transition: State transition S_IDLE -> S_POLICY_ENGINE [ input=I_PE_CALC cause=C_ TIMER_POPPED origin=crm_timer_popped ] Dec 13 00:04:26 server_name_1 crmd[9941]: notice: run_graph: Transition 185166 (Complete=0, Pending=0, Fired=0, Skipped=0, Incomplete=0, Sou rce=/var/lib/pacemaker/pengine/pe-input-656.bz2): Complete Dec 13 00:04:26 server_name_1 crmd[9941]: notice: do_state_transition: State transition S_TRANSITION_ENGINE -> S_IDLE [ input=I_TE_SUCCESS c ause=C_FSA_INTERNAL origin=notify_crmd ] Dec 13 00:08:09 server_name_1 crmd[9941]: notice: throttle_handle_load: High CPU load detected: 3.48 Dec 13 00:09:09 server_name_1 crmd[9941]: notice: throttle_handle_load: High CPU load detected: 5.82 Dec 13 00:09:39 server_name_1 crmd[9941]: notice: throttle_handle_load: High CPU load detected: 4.13 Dec 13 00:10:09 server_name_1 crmd[9941]: notice: throttle_handle_load: High CPU load detected: 4.65 Dec 13 00:10:39 server_name_1 crmd[9941]: notice: throttle_handle_load: High CPU load detected: 6.00 Dec 13 00:11:09 server_name_1 crmd[9941]: notice: throttle_handle_load: High CPU load detected: 5.27 Dec 13 00:11:39 server_name_1 crmd[9941]: notice: throttle_handle_load: High CPU load detected: 4.26 Dec 13 00:12:09 server_name_1 crmd[9941]: notice: throttle_handle_load: High CPU load detected: 3.60 Dec 13 00:12:39 server_name_1 crmd[9941]: notice: throttle_handle_load: High CPU load detected: 3.97 Dec 13 00:13:09 server_name_1 crmd[9941]: notice: throttle_handle_load: High CPU load detected: 3.93 Dec 13 00:14:09 server_name_1 crmd[9941]: notice: throttle_handle_load: High CPU load detected: 3.59 Dec 13 00:17:09 server_name_1 crmd[9941]: notice: throttle_handle_load: High CPU load detected: 3.35 Dec 13 00:18:09 server_name_1 crmd[9941]: notice: throttle_handle_load: High CPU load detected: 3.22 Dec 13 00:18:39 server_name_1 crmd[9941]: notice: throttle_handle_load: High CPU load detected: 3.83 Dec 13 00:19:26 server_name_1 crmd[9941]: notice: do_state_transition: State transition S_IDLE -> S_POLICY_ENGINE [ input=I_PE_CALC cause=C_ TIMER_POPPED origin=crm_timer_popped ] Dec 13 00:19:26 server_name_1 crmd[9941]: notice: run_graph: Transition 185167 (Complete=0, Pending=0, Fired=0, Skipped=0, Incomplete=0, Sou rce=/var/lib/pacemaker/pengine/pe-input-656.bz2): Complete Dec 13 00:19:26 server_name_1 crmd[9941]: notice: do_state_transition: State transition S_TRANSITION_ENGINE -> S_IDLE [ input=I_TE_SUCCESS c ause=C_FSA_INTERNAL origin=notify_crmd ] Dec 13 00:24:09 server_name_1 crmd[9941]: notice: throttle_handle_load: High CPU load detected: 3.77 Dec 13 00:24:39 server_name_1 crmd[9941]: notice: throttle_handle_load: High CPU load detected: 3.36 Dec 13 00:25:09 server_name_1 crmd[9941]: notice: throttle_handle_load: High CPU load detected: 3.79 Dec 13 00:26:09 server_name_1 crmd[9941]: notice: throttle_handle_load: High CPU load detected: 3.47 Dec 13 00:27:09 server_name_1 crmd[9941]: notice: throttle_handle_load: High CPU load detected: 4.89 Dec 13 00:27:39 server_name_1 crmd[9941]: notice: throttle_handle_load: High CPU load detected: 3.29 Dec 13 00:28:09 server_name_1 crmd[9941]: notice: throttle_handle_load: High CPU load detected: 4.04 Dec 13 00:29:09 server_name_1 crmd[9941]: notice: throttle_handle_load: High CPU load detected: 3.34 Dec 13 00:29:39 server_name_1 crmd[9941]: notice: throttle_handle_load: High CPU load detected: 3.25 Dec 13 00:30:39 server_name_1 crmd[9941]: notice: throttle_handle_load: High CPU load detected: 3.31 Dec 13 00:31:09 server_name_1 crmd[9941]: notice: throttle_handle_load: High CPU load detected: 4.88 Dec 13 00:31:39 server_name_1 crmd[9941]: notice: throttle_handle_load: High CPU load detected: 3.89 Dec 13 00:32:09 server_name_1 crmd[9941]: notice: throttle_handle_load: High CPU load detected: 5.32 Dec 13 00:32:39 server_name_1 crmd[9941]: notice: throttle_handle_load: High CPU load detected: 4.38 Dec 13 00:33:09 server_name_1 crmd[9941]: notice: throttle_handle_load: High CPU load detected: 4.43 Dec 13 00:33:39 server_name_1 crmd[9941]: notice: throttle_handle_load: High CPU load detected: 3.48 Dec 13
Re: [ClusterLabs] Pacemaker documentation license clarification
Ken Gaillotwrites: > On 12/11/2015 10:07 AM, Ferenc Wagner wrote: > >> [...] the "Legal Notice" >> section of the generated Publican documentation (for example >> Pacemaker_Explained/desktop/en-US/index.html) says that the material may >> only be distributed under GFDL-1.2+. > > This is an artifact of how you're building the documentation. Easy to > miss given the makefile complexity :) Especially that I did not study the doc makefiles at all, just issued make. > If you look at the generated versions on clusterlabs.org, they have the > correct license (CC-BY-SA) That's great. > However if you do not "make brand" before building the documentation, > you will get the publican defaults. Wouldn't --with-brand=clusterlabs also be needed? Anyway, I can't really do this because of the sudo step. But specifying --brand_dir helps indeed. Is there any reason not to use the clusterlabs brand automatically all the time, without installation? It goes like this: --- a/doc/Makefile.am +++ b/doc/Makefile.am @@ -73,16 +73,20 @@ EXTRA_DIST = $(docbook:%=%.xml) %.html: %.txt $(AM_V_ASCII)$(ASCIIDOC) --unsafe --backend=xhtml11 $< +# publican-clusterlabs/xsl/html-single.xsl imports that of Publican +# through this link during the build +../xsl: + ln -s /usr/share/publican/xsl "$@" CFS_TXT=$(wildcard Clusters_from_Scratch/en-US/*.txt) CFS_XML=$(CFS_TXT:%.txt=%.xml) # We have to hardcode the book name # With '%' the test for 'newness' fails -Clusters_from_Scratch.build: $(PNGS) $(wildcard Clusters_from_Scratch/en-US/*.xml) $(CFS_XML) +Clusters_from_Scratch.build: $(PNGS) $(wildcard Clusters_from_Scratch/en-US/*.xml) $(CFS_XML) ../xsl $(PCMK_V) @echo Building $(@:%.build=%) because of $? rm -rf $(@:%.build=%)/publish/* - $(AM_V_PUB)cd $(@:%.build=%) && RPM_BUILD_DIR="" $(PUBLICAN) build --publish --langs=$(DOCBOOK_LANGS) --formats=$(DOCBOOK_FORMATS) $(PCMK_quiet) + $(AM_V_PUB)cd $(@:%.build=%) && RPM_BUILD_DIR="" $(PUBLICAN) build --publish --langs=$(DOCBOOK_LANGS) --formats=$(DOCBOOK_FORMATS) $(PCMK_quiet) --brand_dir=../publican-clusterlabs rm -rf $(@:%.build=%)/tmp touch $@ [...] -- Thanks, Feri. ___ Users mailing list: Users@clusterlabs.org http://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: Re: SLES11SP4 (crmsh-2.1.2+git49.g2e3fa0e-1.32): problems parsing nodes
>>> Kristoffer Grönlundschrieb am 12.12.2015 um 08:43 in Nachricht <87io443ydc@krigpad.kri.gs>: > Ulrich Windl writes: > >> Hi! >> >> "crm configure edit" displays the nodes section in XML like this: >> >> xml \ >>\ >> \ >> \ >>\ >>\ >> \ >>\ >> >> >> In SLES11 SP3 this was not the case... >> >> The rest of the config is not displayed in XML, just the nodes. > > Hi, > > This may be caused by an unrelated problem with the configuration. crmsh > tries to verify that the CLI syntax truly matches the XML syntax, and > will revert to displaying the XML if it thinks the representation > doesn't match. It can get confused in some cases. > > You might get more information using > > crm -dR configure show h04 Thanks for the hint! Tying it I get some message like these: DEBUG: node!=node: number of children differ In Detail it seems the new software wants to see inside , and does not want to see: So is it too much to expect for an upgrade to fix the XML syntax it it changed? (The output of "cibadmin -Q" does not indicate the XML schema being used) > > In general, for problems upgrading from SLES11SP3 to SLES11SP4 I would > recommend filing issues with SUSE, not upstream. It's not "filing an issue"; it's "make people aware" before they run into the same problems that I did. Regards, Ulrich ___ Users mailing list: Users@clusterlabs.org http://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: Re: Resources start serial, not parralel
Hi! There is one feature in Linux that may affect you: If processes block on I/O (NFS also), the load increases, and the load is the _sum_, and not the _average_ of all CPUs. So if you have many CPUs, your abservable load will typically increase. Recently we had a load of 60, but nobody actually noticed ;-) So maybe you just need to adjust the limits for pacemaker... Regards, Ulrich >>> Oleg Ilyinschrieb am 13.12.2015 um 15:00 in Nachricht