Configuring capacity estimations

The values for capacity estimation needs to be provided based on your available resources for CPU and network. Beside the capacity estimation, you also need to provide information about the broker and partition metrics. You can set the capacity estimations and Kafka properties in Cloudera Manager.

For the rebalancing, you need to provide the capacity values of your resources. These values are used for specifying the rebalancing criteria for your deployment. The following capacity values must be set:


Capacity	Description
`capacity.default.cpu`	100 by default
`capacity.default.network-in`	Given by the internet provider
`capacity.default.network-out`	Given by the internet provider

The optimizers in Cruise Control use the network incoming and outgoing capacities to define a boundary for optimization. The capacity estimates are generated and read by Cruise Control. A capacity.json file is generated when Cruise Control is started. When a new broker is added, Cruise Control uses the default broker capacity values. However, in case disk related goals are used, Cruise Control must be restarted to load the actual disk capacity metrics of the new broker.

The following table lists all the configurations that are needed to configure Cruise Control specifically to your environment:


Configuration	Description
`num.metric.fetchers`	Parallel threads for fetching metrics from the Cloudera Manager database
`partition.metric.sample.store.topic`	Storing Cruise Control metrics
`broker.metric.sample.store.topic`	Storing Cruise Control metircs
`partition.metrics.window.ms`	Time window size for partition metrics
`broker.metrics.window.ms`	Time window size for broker metrics
`num.partition.metrics.windows`	Number of stored partition windows
`num.broker.metrics.windows`	Number of stored broker windows