low severityZilliz Cloud (vector DB service)
Cluster fails to auto-scale (no scale-out during high load or scale-in during low), stuck in 'Modifying' status, write failures despite available reads, or support notifications for limit violations. No error codes specific to 'threshold configuration'.
Root cause
No documented bug; potential issues from violating scaling prerequisites/limits (e.g., insufficient CUs, data >80% capacity, exceeding CU x replica max) causing resource check failures during auto-scale attempts. Thresholds are fixed/system-managed, not user-configurable, eliminating misconfiguration.
Zilliz CloudautoscalingreplicaCU capacityCU computationscaling limits