Re: [ClusterLabs] a resource being all -infinity
On Wed, 2019-11-06 at 18:19 +0800, 张冲andy wrote:
>
> How do I avoid a resource being -infinity at all nodes,There is no
> way to switch successfully when a disaster occurs. Such
> as, HAProxy_43234 is all -infinity. Looking forward to your reply
> . Thank you very much
Hi,
The most common factors in scores are constraints and stickiness. If
you run "cibadmin --query --scope=constraints" (or the equivalent in a
higher-level tool), you can see what constraints are in effect.
Other things that can affect scores include previous failures of the
resource on a node, and whether you have configured advanced features
such as the symmetric-cluster property, utilization attributes, or node
health monitoring.
>
> Version information:
> root@dc-dcb-corosync-haproxy-07:~# uname -a
> Linux dc-dcb-corosync-haproxy-07 4.4.0-142-generic #168-Ubuntu SMP
> Wed Jan 16 21:00:45 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
> root@dc-dcb-corosync-haproxy-07:~# corosync -v
> Corosync Cluster Engine, version '2.3.5'
> Copyright (c) 2006-2009 Red Hat, Inc.
> root@dc-dcb-corosync-haproxy-07:~# pacemakerd --version
> Pacemaker 1.1.14
>
>
>
> Configuration information:
> root@dc-dcb-corosync-haproxy-08:~# cat /etc/corosync/corosync.conf
> totem {
> version: 2
> threads: 8
> secauth: on
> token: 1000
> token_retransmits_before_loss_const: 10
> cluster_name: dba_cluster_3
> transport: udpu
> interface {
> ringnumber: 0
> bindnetaddr: current-node
> #broadcast: yes
> mcastaddr: 226.1.1.3
> mcastport: 6407
> ttl: 1
> }
> }
>
> logging {
> fileline: off
> to_logfile: yes
> to_syslog: no
> logfile: /data/corosync/corosync.log
> timestamp: on
> debug: on
> logger_subsys {
> subsys: AMF
> debug: off
> }
> }
>
> service {
> ver: 0
> name: pacemaker
> }
>
> quorum {
> provider: corosync_votequorum
> expected_votes: 2
> wait_for_all: 1
> last_man_standing: 1
> last_man_standing_window: 1
> ## two_node: 1
> }
>
> nodelist {
> node {
> ring0_addr: dc-dcb-corosync-haproxy-07
> nodeid: 1
> }
> node {
> ring0_addr: dc-dcb-corosync-haproxy-08
> nodeid: 2
> }
> node {
> ring0_addr: dc-dcb-corosync-haproxy-09
> nodeid: 3
> }
> }
>
>
>
> root@dc-dcb-corosync-haproxy-08:~# crm_simulate -sL
> Current cluster status:
> Online: [ dc-dcb-corosync-haproxy-07 dc-dcb-corosync-haproxy-08 ]
> OFFLINE: [ dc-dcb-corosync-haproxy-09 ]
>
> Resource Group: HAProxyGroup_test1_43231
> HAProxyVIP_43231 (ocf::heartbeat:IPaddr):Started dc-dcb-
> corosync-haproxy-07
> HAProxy_43231(systemd:haproxy43231): Started dc-dcb-
> corosync-haproxy-07
> Resource Group: HAProxyGroup_test2_43232
> HAProxyVIP_43232 (ocf::heartbeat:IPaddr):Started dc-dcb-
> corosync-haproxy-08
> HAProxy_43232(systemd:haproxy43232): Started dc-dcb-
> corosync-haproxy-08
> Resource Group: HAProxyGroup_test3_43233
> HAProxyVIP_43233 (ocf::heartbeat:IPaddr):Started dc-dcb-
> corosync-haproxy-08
> HAProxy_43233(systemd:haproxy43233): Started dc-dcb-
> corosync-haproxy-08
> Resource Group: HAProxyGroup_test4_43234
> HAProxyVIP_43234 (ocf::heartbeat:IPaddr):Stopped
> HAProxy_43234(systemd:haproxy43234): Stopped
>
> Allocation scores:
> group_color: HAProxyGroup_test1_43231 allocation score on dc-dcb-
> corosync-haproxy-07: 0
> group_color: HAProxyGroup_test1_43231 allocation score on dc-dcb-
> corosync-haproxy-08: 0
> group_color: HAProxyGroup_test1_43231 allocation score on dc-dcb-
> corosync-haproxy-09: 0
> group_color: HAProxyVIP_43231 allocation score on dc-dcb-corosync-
> haproxy-07: 0
> group_color: HAProxyVIP_43231 allocation score on dc-dcb-corosync-
> haproxy-08: 0
> group_color: HAProxyVIP_43231 allocation score on dc-dcb-corosync-
> haproxy-09: 0
> group_color: HAProxy_43231 allocation score on dc-dcb-corosync-
> haproxy-07: 0
> group_color: HAProxy_43231 allocation score on dc-dcb-corosync-
> haproxy-08: 0
> group_color: HAProxy_43231 allocation score on dc-dcb-corosync-
> haproxy-09: 0
> native_color: HAProxyVIP_43231 allocation score on dc-dcb-corosync-
> haproxy-07: 0
> native_color: HAProxyVIP_43231 allocation score on dc-dcb-corosync-
> haproxy-08: 0
> native_color: HAProxyVIP_43231 allocation score on dc-dcb-corosync-
> haproxy-09: -INFINITY
> native_color: HAProxy_43231 allocation score on dc-dcb-corosync-
> haproxy-07: 0
> native_color: HAProxy_43231 allocation score on dc-dcb-corosync-
> haproxy-08: -INFINITY
> native_color: HAProxy_43231 allocation score on dc-dcb-corosync-
> haproxy-09: -INFINITY
> group_color: HAProxyGroup_test2_43232 allocation score on dc-dcb-
> corosync-haproxy-07: 0
> group_color: HAProxyGroup_test2_43232 allocation score on dc-dcb-
> corosync-haproxy-08: 0
> group_color: HAProxyGroup_test2_43232 allocation score on dc-dcb-
> corosync-haproxy-09: 0
> group_color: HAProxyVIP_43232 allocation score on dc-dcb-corosync-
> haproxy-07: 0
> group_col
[ClusterLabs] a resource being all -infinity
How do I avoid a resource being -infinity at all nodes,There is no way to
switch successfully when a disaster occurs. Such as, HAProxy_43234 is
all -infinity. Looking forward to your reply . Thank you very
much
Version information:
root@dc-dcb-corosync-haproxy-07:~# uname -a
Linux dc-dcb-corosync-haproxy-07 4.4.0-142-generic #168-Ubuntu SMP Wed Jan 16
21:00:45 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
root@dc-dcb-corosync-haproxy-07:~# corosync -v
Corosync Cluster Engine, version '2.3.5'
Copyright (c) 2006-2009 Red Hat, Inc.
root@dc-dcb-corosync-haproxy-07:~# pacemakerd --version
Pacemaker 1.1.14
Configuration information:
root@dc-dcb-corosync-haproxy-08:~# cat /etc/corosync/corosync.conf
totem {
version: 2
threads: 8
secauth: on
token: 1000
token_retransmits_before_loss_const: 10
cluster_name: dba_cluster_3
transport: udpu
interface {
ringnumber: 0
bindnetaddr: current-node
# broadcast: yes
mcastaddr: 226.1.1.3
mcastport: 6407
ttl: 1
}
}
logging {
fileline: off
to_logfile: yes
to_syslog: no
logfile: /data/corosync/corosync.log
timestamp: on
debug: on
logger_subsys {
subsys: AMF
debug: off
}
}
service {
ver: 0
name: pacemaker
}
quorum {
provider: corosync_votequorum
expected_votes: 2
wait_for_all: 1
last_man_standing: 1
last_man_standing_window: 1
## two_node: 1
}
nodelist {
node {
ring0_addr: dc-dcb-corosync-haproxy-07
nodeid: 1
}
node {
ring0_addr: dc-dcb-corosync-haproxy-08
nodeid: 2
}
node {
ring0_addr: dc-dcb-corosync-haproxy-09
nodeid: 3
}
}
root@dc-dcb-corosync-haproxy-08:~# crm_simulate -sL
Current cluster status:
Online: [ dc-dcb-corosync-haproxy-07 dc-dcb-corosync-haproxy-08 ]
OFFLINE: [ dc-dcb-corosync-haproxy-09 ]
Resource Group: HAProxyGroup_test1_43231
HAProxyVIP_43231(ocf::heartbeat:IPaddr):Started
dc-dcb-corosync-haproxy-07
HAProxy_43231 (systemd:haproxy43231): Started
dc-dcb-corosync-haproxy-07
Resource Group: HAProxyGroup_test2_43232
HAProxyVIP_43232(ocf::heartbeat:IPaddr):Started
dc-dcb-corosync-haproxy-08
HAProxy_43232 (systemd:haproxy43232): Started
dc-dcb-corosync-haproxy-08
Resource Group: HAProxyGroup_test3_43233
HAProxyVIP_43233(ocf::heartbeat:IPaddr):Started
dc-dcb-corosync-haproxy-08
HAProxy_43233 (systemd:haproxy43233): Started
dc-dcb-corosync-haproxy-08
Resource Group: HAProxyGroup_test4_43234
HAProxyVIP_43234(ocf::heartbeat:IPaddr):Stopped
HAProxy_43234 (systemd:haproxy43234): Stopped
Allocation scores:
group_color: HAProxyGroup_test1_43231 allocation score on
dc-dcb-corosync-haproxy-07: 0
group_color: HAProxyGroup_test1_43231 allocation score on
dc-dcb-corosync-haproxy-08: 0
group_color: HAProxyGroup_test1_43231 allocation score on
dc-dcb-corosync-haproxy-09: 0
group_color: HAProxyVIP_43231 allocation score on dc-dcb-corosync-haproxy-07: 0
group_color: HAProxyVIP_43231 allocation score on dc-dcb-corosync-haproxy-08: 0
group_color: HAProxyVIP_43231 allocation score on dc-dcb-corosync-haproxy-09: 0
group_color: HAProxy_43231 allocation score on dc-dcb-corosync-haproxy-07: 0
group_color: HAProxy_43231 allocation score on dc-dcb-corosync-haproxy-08: 0
group_color: HAProxy_43231 allocation score on dc-dcb-corosync-haproxy-09: 0
native_color: HAProxyVIP_43231 allocation score on dc-dcb-corosync-haproxy-07: 0
native_color: HAProxyVIP_43231 allocation score on dc-dcb-corosync-haproxy-08: 0
native_color: HAProxyVIP_43231 allocation score on dc-dcb-corosync-haproxy-09:
-INFINITY
native_color: HAProxy_43231 allocation score on dc-dcb-corosync-haproxy-07: 0
native_color: HAProxy_43231 allocation score on dc-dcb-corosync-haproxy-08:
-INFINITY
native_color: HAProxy_43231 allocation score on dc-dcb-corosync-haproxy-09:
-INFINITY
group_color: HAProxyGroup_test2_43232 allocation score on
dc-dcb-corosync-haproxy-07: 0
group_color: HAProxyGroup_test2_43232 allocation score on
dc-dcb-corosync-haproxy-08: 0
group_color: HAProxyGroup_test2_43232 allocation score on
dc-dcb-corosync-haproxy-09: 0
group_color: HAProxyVIP_43232 allocation score on dc-dcb-corosync-haproxy-07: 0
group_color: HAProxyVIP_43232 allocation score on dc-dcb-corosync-haproxy-08: 0
group_color: HAProxyVIP_43232 allocation score on dc-dcb-corosync-haproxy-09: 0
group_color: HAProxy_43232 allocation score on dc-dcb-corosync-haproxy-07: 0
group_color: HAProxy_43232 allocation score on dc-dcb-corosync-haproxy-08: 0
group_color: HAProxy_43232 allocation score on dc-dcb-corosync-haproxy-09: 0
native_color: HAProxyVIP_43232 allocation score on dc-dcb-corosync-haproxy-07: 0
native_color: HAProxyVIP_43232 allocation score on dc-dcb-corosync-haproxy-08: 0
native_color: HAProxyVIP_43232 allocation score on dc-dcb-corosync-haproxy-09:
-INFINITY
native_color: HAProxy_43232 allocation score on dc-dcb-corosync-haproxy-07:
-INFINITY
native_color: HAProxy_43232 all
