From aa9158c046a8e172c95e71d221154206852c699d Mon Sep 17 00:00:00 2001 From: Vishesh Date: Thu, 18 Jan 2024 13:20:47 +0530 Subject: [PATCH] Document advance DRS settings --- source/adminguide/clusters.rst | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) diff --git a/source/adminguide/clusters.rst b/source/adminguide/clusters.rst index 1c8f131693..688c3e882c 100644 --- a/source/adminguide/clusters.rst +++ b/source/adminguide/clusters.rst @@ -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 paramters 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.