Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 24 additions & 0 deletions source/adminguide/clusters.rst
Original file line number Diff line number Diff line change
Expand Up @@ -74,6 +74,30 @@ Following are the configuration parameters for DRS.
Very high value for ``drs.max.migrations`` can result in management server using up all of it's workers for DRS tasks
and not being able to execute other tasks.

There are some advanced parameters that can be configured for DRS. These parameters impact the way imbalance is calculated
for a cluster. Do not change these parameters unless you know what you are doing.

.. list-table:: Advanced DRS related cluster parameters
:header-rows: 1

* - Parameter
- Default
- Description
* - ``drs.metric.type``
- `used`
- The metric type used to measure imbalance in a cluster. This can completely change the imbalance value.
Possible values are free, used.
* - ``drs.metric.use.ratio``
- `true`
- Whether to use ratio of selected metric & total. Useful when the cluster has hosts with different capacities.
* - ``drs.imbalance.condensed.skip.threshold``
- `0.95`
- Threshold to ignore the metric for a host while calculating the imbalance to decide whether DRS is required for
a cluster. This is to avoid cases when the calculated imbalance gets skewed due to a single host having a very
high/low metric value resulting in imbalance being higher than 1. If ``drs.metric.type`` is ``free``, set a lower
value and if it is ``used`` set a higher value. The value should be between `0.0` and `1.0`.
This is applicable only for Condensed algorithm.

Executing manual DRS on a cluster
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DRS can also be manually executed for a cluster.
Expand Down