Michael Gruben Trejo

Feature Request: Broker-Ejection Interface

2

# Background `cruise-control` manages the distribution of replicas across brokers in a kafka cluster, according to proposals that it calculates for optimal resource utilization. `cruise-control` also has the concept of...

cruise-control-client is not API complete with cruise-control

3

# Problem Currently, `cruise-control-client` lags behind `cruise-control` in the parameters that are available to some of its endpoints. All the endpoints are there, so a user with the `cruise-control` documentation...

Self-healing can forever "miss" broker failures that occur while it is disabled

2

# Background `cruise-control` provides [self-healing](https://github.com/linkedin/cruise-control/blob/master/cruise-control/src/yaml/endpoints/admin.yaml#L13) for a variety of anomalies. When an anomaly is detected, and the corresponding self-healing `boolean` is enabled, `cruise-control` can generate a proposal on its own...

# Background `cruise-control-client` allows for users to specify the `parameter=value` pairs for the endpoint. For parameters that `cruise-control-client` has implemented (like `json`, under `JSONParameter`), `cruise-control-client` performs additional verification to ensure...

# Background Currently, `cruise-control` provides (among others) the following goals: * `LeaderBytesInDistributionGoal` * `NetworkInboundUtilDistributionGoal` * `LeaderReplicaDistributionGoal` The load on individual `kafka` brokers can be highly dependent on the rate of...