.
In that case, does it mean that 3 web server groups are weighted the same as 2
database groups in terms of distribution?
Ilia
> On Feb 17, 2017, at 2:58 AM, Kristoffer Grönlund wrote:
>
> Ilia Sokolinski writes:
>
>> Suppose I have a N node cluster where N > 2
ill pacemaker redistribute the resources equally too, e.g. m
* N/(N-1) per node?
I don’t see any settings controlling this behavior in the documentation, but
perhaps, pacemaker tries to be “fair” by default.
Thanks
Ilia Sokolinski
___
Users mailing l
>
> I'm not sure there's a way to do this.
>
> If a (non-reloadable) parameter changes, the entire clone does need a
> restart, so the cluster will want all instances to be stopped, before
> proceeding to start them all again.
>
> Your desired behavior couldn't be the default, because not all s
ction, but there is no notify about the reload
action, so it does not work.
Any other suggestions?
Thanks a lot
Ilia
> On Jun 10, 2016, at 3:13 AM, Ferenc Wágner wrote:
>
> Ilia Sokolinski writes:
>
>> We have a custom Master-Slave resource running on a 3-node pcs cl
Feri,
Thanks for the answer - this is very useful.
Ilia
> On Jun 10, 2016, at 3:13 AM, Ferenc Wágner wrote:
>
> Ilia Sokolinski writes:
>
>> We have a custom Master-Slave resource running on a 3-node pcs cluster on
>> CentOS 7.1
>>
>> As part of what i
Hi,
We have a custom Master-Slave resource running on a 3-node pcs cluster on
CentOS 7.1
As part of what is supposed to be an NDU we do update some properties of the
resource.
For some reason this causes both Master and Slave instances of the resource to
be restarted.
Since restart takes a f
Hi,
What are the best practices with respect to using DNS names vs IP addresses in
pacemaker/corosync configuration?
Thanks
Ilia Sokolinski
___
Users mailing list: Users@clusterlabs.org
http://clusterlabs.org/mailman/listinfo/users
Project Home
node {
>> ring0_addr: 42-hw-back-1.clearsky-data.net
>> nodeid: 1
>>}
>> node {
>> ring0_addr: 41-hw-back-1.clearsky-data.net
>> nodeid: 2
>>}
>> node {
>> ring0_addr: dq-ceph9.clear
messages mean, and how can we stop them?
Any help would be very appreciated.
Ilia Sokolinski
PS
I have tried to enable corosync debug and got the following logs:
Oct 8 16:18:47 42-hw-rig4-L3-2 corosync[15105]: [CFG ] Config reload
requested by node 1
Oct 8 16:18:47 42-hw-rig4-L3-2 corosync
