Skip to content

feat(enterprise): cluster health verification commands #626

@joshrotenberg

Description

@joshrotenberg

Overview

Add enterprise cluster health verification commands to help operators ensure their Redis Enterprise clusters are properly configured and balanced.

This consolidates #418 (cluster balance verification) and #419 (rack-aware verification) into a single backlog item.

Proposed Commands

1. Shard Balance Verification

Verify that shards are evenly distributed across nodes in the cluster.

redisctl enterprise cluster verify-balance

Checks:

  • Shard count per node
  • Memory utilization per node
  • Identify nodes that are over/under-utilized
  • Suggest rebalancing if needed

Output example:

Node    Shards  Memory Used  Status
node1   12      45%          OK
node2   14      52%          OK
node3   8       31%          UNDER-UTILIZED

Warning: Cluster is imbalanced. Consider running 'rladmin rebalance'

2. Rack-Aware Verification

Verify that master and replica shards are placed on different racks for high availability.

redisctl enterprise cluster verify-rack-awareness

Checks:

  • Master/replica placement across racks
  • Identify databases with HA violations
  • Check rack zone configuration

Output example:

Database    Masters  Replicas  Rack Distribution  Status
db:1        3        3         rack1/rack2        OK
db:2        2        2         rack1/rack1        VIOLATION

Error: db:2 has master and replica on same rack

3. Combined Health Check

redisctl enterprise cluster health

Runs all verification checks and provides a summary report.

Implementation Notes

  • Use existing Enterprise API endpoints for node/shard/database info
  • Consider adding --json output for scripting
  • Add --fix flag to suggest or execute remediation (future)
  • Consider MCP tool integration for AI-assisted troubleshooting

Related

Metadata

Metadata

Assignees

No one assigned

    Labels

    enterpriseRelated to Redis Enterprise functionality

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions