FWIW, this is probably more suited to the users list > On 13 Aug 2015, at 11:09 pm, Nekrasov, Alexander <[email protected]> > wrote: > > Hello, > > I have a dependency tree starting with PgsqlShared as root, and two sub trees: > 1. PgsqlShared->apache->apl->c4fastvpa (i.e. apache has an AFTER > constrain on PgsqlShared, etc.) > 2. PgsqlShared->iproute > > With the version on Pacemaker that came with SLES11, the starting was done in > parallel, such as > 1. PgsqlShared > 2. apache and iproute – parallel, as expected > 3. apl > 4. c4fastvpa > > With the version of Pacemaker that comes with SLES12, the starting is serial: > 1. PgsqlShared > 2. apache > 3. apl > 4. c4fastvpa > 5. iproute – delayed until the first sub tree completes
Based on? Remember we can’t see what you see. What is your configuration? Logs? > > I have searched for solutions and found a number of variables that should > affect this area. I tried to set all of them in different combinations, to no > effect. > > 20:18:40 root@BC-H1008-spb spb:~> echo $LRMD_MAX_CHILDREN > 30 > 20:18:45 root@BC-H1008-spb spb:~> echo $PCMK_MAX_CHILDREN > 30 > 20:05:56 root@BC-H1008-spb spb:~> crm_attribute -Q --name batch-limit > 30 > 20:06:01 root@BC-H1008-spb spb:~> crm_attribute -Q --type nodes --node spb > --name node-action-limit > 30 > 20:06:28 root@BC-H1008-spb spb:~> crm_attribute -Q --name migration-limit > -1 > > Any pointers appreciated. > > libpacemaker3-1.1.12-7.1.x86_64 > pacemaker-1.1.12-7.1.x86_64 > pacemaker-debuginfo-1.1.12-7.1.x86_64 > pacemaker-cli-1.1.12-7.1.x86_64 > > Thanks, > Alexander > > > > _______________________________________________ > Developers mailing list > [email protected] > http://clusterlabs.org/mailman/listinfo/developers _______________________________________________ Developers mailing list [email protected] http://clusterlabs.org/mailman/listinfo/developers
