Revision 325947e7 man/hbal.rst
b/man/hbal.rst | ||
---|---|---|
91 | 91 |
|
92 | 92 |
- a node to go into N+1 failure state |
93 | 93 |
- an instance to move onto an offline node (offline nodes are either |
94 |
read from the cluster or declared with *-O*) |
|
94 |
read from the cluster or declared with *-O*; drained nodes are |
|
95 |
considered offline) |
|
95 | 96 |
- an exclusion-tag based conflict (exclusion tags are read from the |
96 | 97 |
cluster and/or defined via the *\--exclusion-tags* option) |
97 | 98 |
- a max vcpu/pcpu ratio to be exceeded (configured via *\--max-cpu*) |
... | ... | |
102 | 103 |
~~~~~~~~~~~~~~~ |
103 | 104 |
|
104 | 105 |
As said before, the algorithm tries to minimise the cluster score at |
105 |
each step. Currently this score is computed as a sum of the following
|
|
106 |
components: |
|
106 |
each step. Currently this score is computed as a weighted sum of the
|
|
107 |
following components:
|
|
107 | 108 |
|
108 | 109 |
- standard deviation of the percent of free memory |
109 | 110 |
- standard deviation of the percent of reserved memory |
110 | 111 |
- standard deviation of the percent of free disk |
111 | 112 |
- count of nodes failing N+1 check |
112 | 113 |
- count of instances living (either as primary or secondary) on |
113 |
offline nodes |
|
114 |
offline nodes; in the sense of hbal (and the other htools) drained |
|
115 |
nodes are considered offline |
|
114 | 116 |
- count of instances living (as primary) on offline nodes; this |
115 | 117 |
differs from the above metric by helping failover of such instances |
116 | 118 |
in 2-node clusters |
Also available in: Unified diff