>>> Andrei Borzenkov schrieb am 27.03.2018 um 17:46 in
Nachricht <41848ce9-39f1-d91e-771b-683beef73...@gmail.com>:
> "Original" for lack of better word. To explain - "crm_simulate -s" will
> show final scores as determined by possible colocation contraints. E.g.
> if B is
Thought I would share an experience with the community. We have RHEL 7.4
clusters that uses the heartbeat LVM resource (HA-LVM volume group). The LVM
resource does a "vgscan --cache" command as part of its monitoring routine.
We have found that the pvmove command option "-i0" will block the
On Tue, 2018-03-27 at 18:46 +0300, Andrei Borzenkov wrote:
> "Original" for lack of better word. To explain - "crm_simulate -s"
> will
> show final scores as determined by possible colocation contraints.
> E.g.
> if B is colocated with A, scores for A will be adjusted by scores for
> B.
> In large
"Original" for lack of better word. To explain - "crm_simulate -s" will
show final scores as determined by possible colocation contraints. E.g.
if B is colocated with A, scores for A will be adjusted by scores for B.
In large or dynamic configuration with multiple constraints it may not
be exactly
Jing,
Jan,
Thanks so much for your reply. Can I just use the 1.4.7 spec file, swap the
version number to build corosync for CentOS6? Do I have to build the
configure + make + make install works for sure.
Going RPM way is probably cleaner, but honestly I have no experience
with this path. I
Jan,
Thanks so much for your reply. Can I just use the 1.4.7 spec file, swap the
version number to build corosync for CentOS6? Do I have to build the same
version of corosync-lib to work with it? What would be the best version to
build? I have installed pacemaker 1.1.15-5.
-Jing
On Mon, Mar 26,
Hello Ken,
here is the output of my other 2 clusters.
*cluster 0:*
Location Constraints:
Ordering Constraints:
Colocation Constraints:
virtual_ip with vg1 (score:INFINITY)
virtual_ip with lv1 (score:INFINITY)
virtual_ip with nfs-daemon (score:INFINITY)
virtual_ip with lv1_export