kafka.server.ReplicaManager.UnderReplicatedPartitions
The number of under-replicated partitionsDimensions:None
Technical Annotations (19)
Configuration Parameters (5)
spec.replicasrecommended: minimum 3confluent.balancer.replication.in.max.bytes.per.secondrecommended: >= (RF-1) * confluent.balancer.producer.in.max.bytes.per.secondreplica.fetch.max.bytesrecommended: >= message.max.bytesmessage.max.bytesrecommended: 1048576 (1MB default)min.insync.replicasrecommended: 2Error Signatures (2)
NotEnoughReplicasexceptionNotEnoughReplicasAfterAppendexceptionCLI Commands (1)
kubectl scale kafka <Kafka-CR-name> --replicas=NremediationTechnical References (11)
in-sync replicasconceptconsumer groupcomponentISR churnconceptpage cache hit ratioconceptISRconceptConfluent Control Centercomponentpartition reassignmentconceptunder-replicated partitionsconceptreplicaconceptreplication factorconceptminIsrcomponentRelated Insights (12)
Negative out-of-sync replica count after broker recoveryinfo
▸
Under-replicated partitions indicate data loss risk on broker failurecritical
▸
ISR shrinkage progresses silently until data loss occurscritical
▸
Consumer lag escalates rapidly while broker health metrics remain normalcritical
▸
Missing monitoring of ISR shrinks and consumer lag delays incident responsewarning
▸
Scaling below 3 replicas violates default replication factorcritical
▸
Replication inbound throttle insufficient for replication factor causes ISR issueswarning
▸
Broker removal in pre-7.0 versions causes under-replicated partitionscritical
▸
Under-replicated partitions indicate data durability riskwarning
▸
Replication failures when replica fetch limit smaller than message limitcritical
▸
Producer writes fail when in-sync replicas drop below minimum thresholdcritical
▸
Partitions fall below minimum in-sync replica countcritical
▸