Hi All,
When a user changes the globally-unique attribute of the resource, a problem
occurs.
When it manages the resource with PID file, this occurs, but this is because
PID file name changes by globally-unique attribute.
(snip)
if [ ${OCF_RESKEY_CRM_meta_globally_unique} = false ]; then
I use Debian 7 and got:
Reconnecting...root@a:~# crm_resource --resource msPostgresql --ban
--master --host a.geocluster.e-autopay.com
crm_resource: unrecognized option '--ban'
No other way to move master?
2014/1/13 Andrew Beekhof and...@beekhof.net
On 13 Jan 2014, at 8:32 pm, Andrey
14.01.2014, 12:39, "Andrey Rogovsky" a.rogov...@gmail.com:I use Debian 7 and got:Reconnecting...root@a:~# crm_resource --resource msPostgresql --ban --master --host a.geocluster.e-autopay.comcrm_resource: unrecognized option '--ban' No other way to move master? 2014/1/13 Andrew Beekhof
I understand it. So, no way change master better without cluster software
update?
2014/1/14 Andrey Groshev gre...@yandex.ru
14.01.2014, 12:39, Andrey Rogovsky a.rogov...@gmail.com:
I use Debian 7 and got:
Reconnecting...root@a:~# crm_resource --resource msPostgresql --ban
--master
14.01.2014, 15:37, "Andrey Rogovsky" a.rogov...@gmail.com:I understand it. So, no way change master better without cluster software update? You can send a node in standby (crm_stanbdy).All resources will move to another node (if available).Pgsql resource agent will promote postgresql on another
On Mon, Nov 11, 2013 at 1:52 AM, Andrew Beekhof and...@beekhof.net wrote:
On 16 Oct 2013, at 12:21 am, Juraj Fabo juraj.f...@gmail.com wrote:
Juraj Fabo juraj.fabo@... writes:
Hello Andrew
thank you for the response.
I've patched crmd, cleaned the cluster, done the scenario
Hello,
I am running on SUSE Linux and recently upgraded to pacemaker 1.1.10. Here
are my RPM levels:
pacemaker-mgmt-2.1.2-0.11.4
pacemaker-mgmt-client-2.1.2-0.11.4
pacemaker-1.1.10-0.9.28
When I migrate a resource group, I get the new cli-ban- location constraint
appear in the CIB.
Crm
On Tue, 2014-01-14 at 16:01 +1100, Andrew Beekhof wrote:
On Tue, 2014-01-14 at 08:09 +1100, Andrew Beekhof wrote:
The local cib hasn't caught up yet by the looks of it.
I should have asked in my previous message: is this entirely an artifact
of having just restarted or are there any
14.01.2014, 10:00, Andrey Groshev gre...@yandex.ru:
14.01.2014, 07:47, Andrew Beekhof and...@beekhof.net:
Ok, here's what happens:
1. node2 is lost
2. fencing of node2 starts
3. node2 reboots (and cluster starts)
4. node2 returns to the membership
5. node2 is marked as a cluster
Thanks a lot.
2014/1/14 Andrey Groshev gre...@yandex.ru
14.01.2014, 15:37, Andrey Rogovsky a.rogov...@gmail.com:
I understand it. So, no way change master better without cluster software
update?
You can send a node in standby (crm_stanbdy).
All resources will move to another node
On 14 Jan 2014, at 10:32 pm, Andrey Rogovsky a.rogov...@gmail.com wrote:
I understand it. So, no way change master better without cluster software
update?
crm_resource is just creating (and removing) normal location constraints.
no reason you couldn't write a script to create them instead.
On 15 Jan 2014, at 12:15 am, Andrey Groshev gre...@yandex.ru wrote:
14.01.2014, 10:00, Andrey Groshev gre...@yandex.ru:
14.01.2014, 07:47, Andrew Beekhof and...@beekhof.net:
Ok, here's what happens:
1. node2 is lost
2. fencing of node2 starts
3. node2 reboots (and cluster
On 14 Jan 2014, at 7:26 pm, renayama19661...@ybb.ne.jp wrote:
Hi All,
When a user changes the globally-unique attribute of the resource, a
problem occurs.
When it manages the resource with PID file, this occurs, but this is because
PID file name changes by globally-unique attribute.
Hi Andrew,
Thank you for comment.
But, the resource does not stop because PID file was changed as for the
changed resource of the globally-unique attribute.
I'd have expected the stop action to be performed with the old attributes.
crm_report tarball?
Okay.
I register this topic with
On 15 Jan 2014, at 12:06 pm, renayama19661...@ybb.ne.jp wrote:
Hi Andrew,
Sorry
This problem is a thing of Pacemaker1.0.
On Pacemaker1.1.11, the resource did movement to stop definitely.
When globally-unique attribute changed somehow or other in Pacemaker1.1,
Pacemkaer seems to
On 14 Jan 2014, at 11:25 pm, Juraj Fabo juraj.f...@gmail.com wrote:
Hi
I have master-slave cluster with configuration attached below.
It is based on documented postgresql master-slave cluster configuration.
Colocation constraints should work that way that if some of master-group
On 14 Jan 2014, at 11:50 pm, Brian J. Murrell (brian) br...@interlinx.bc.ca
wrote:
On Tue, 2014-01-14 at 16:01 +1100, Andrew Beekhof wrote:
On Tue, 2014-01-14 at 08:09 +1100, Andrew Beekhof wrote:
The local cib hasn't caught up yet by the looks of it.
I should have asked in my
17 matches
Mail list logo
