Ross ROSS = Recommend OSS · open-source software intelligence for agents

cruise-control-for-kafka/cruise-control

Cruise-control is the first of its kind to fully automate the dynamic workload rebalance and self-healing of a Kafka cluster. It provides great value to Kafka users by simplifying the operation of Kafka clusters. observed · 2026-10-11

github.com/cruise-control-for-kafka/cruise-control · homepage · Java · Apache-2.0 (permissive) observed · 2026-10-11

Health v2 · maintenance only

91/100

  • Activity 99
  • Release rhythm 75
  • Longevity 100
How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-10-21. Adoption (stars, forks) is never an input.

  • gap_med: 33
  • age_days: 3353
  • days_rel: 89
  • days_push: 11
  • n_releases_24m: 8

Full methodology

Adoption not part of the score

3046 stars · 653 forks observed · 2026-10-11

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

Cruise Control is a Java-based service that automates dynamic workload rebalancing and self-healing for Apache Kafka clusters. It tracks broker resource utilization, generates multi-goal rebalance proposals, detects anomalies like broker failures, and performs admin operations such as adding or removing brokers.

Use cases

  • automatically rebalance my kafka cluster
  • detect and self-heal broker failures in kafka
  • generate rebalance proposals for rack-aware replica placement
  • monitor resource utilization across kafka brokers
  • safely decommission kafka brokers without downtime
  • fix offline replicas and adjust replication factor
  • detect slow brokers and metric anomalies in kafka

When to choose

  • you operate large kafka clusters with hundreds of brokers where manual rebalancing is impractical
  • you need automated anomaly detection and self-healing for kafka
  • you want rack-aware, capacity-aware replica placement optimization

When to avoid

  • you run small kafka clusters where manual partition reassignment is sufficient
  • you use a message broker other than apache kafka
  • you cannot run an additional jvm service alongside your kafka cluster

Facets

service · maturity active

monitoring alerting configuration-management deployment analytics microservices monitoring self-hosted infrastructure-as-code jvm self-hosted kafka cluster-rebalancing self-healing anomaly-detection broker-management linkedin devops linux docker

2 sources

Member repositories

RepositoryRoleHealth v2
cruise-control-for-kafka/cruise-controlmain91

For agents

markdown · JSON · MCP: product_card(name="cruise-control-for-kafka/cruise-control")

Data as of 2026-10-19T08:05:51.212177+00:00 · Report a problem