You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
152699: kvserver: add ReplicateQueueMaxSize r=tbg a=wenyihu6
Informs: #151775
Release note: none
---
**kvserver: add ReplicateQueueDroppedDueToSize**
Previously, we had limited observability into when queues drop replicas due to
reaching their maximum size. This commit adds a metric to track and observe such
events.
---
**kvserver: add BaseQueueMaxSize and ReplicateQueueMaxSize**
Previously, the max base queue size was hardcoded to defaultQueueMaxSize
(10000). Since replica item structs in the priority queue are small, we don’t
see a strong reason for this fixed limit. As an incremental and backport
friendly change, this commit makes the queue size configurable via a cluster
setting. The replicate queue uses its own setting, allowing its size to be
increased independently while leaving other queues unchanged.
---
**kvserver: add TestBaseQueueMaxSize**
This commit adds tests to (1) verify metric updates when replicas are dropped
from the queue, and (2) ensure the cluster setting for configuring the base
queue’s max size works correctly.
---
**Revert "kvserver: add TestBaseQueueMaxSize"**
This reverts commit a5f01e5.
---
**Revert "kvserver: add BaseQueueMaxSize and ReplicateQueueMaxSize"**
This reverts commit d89eaa7.
---
**kvserver: add ReplicateQueueMaxSize**
Previously, the maximum base queue size was hardcoded to defaultQueueMaxSize
(10000). Since replica item structs are small, there’s little reason to enforce
a fixed limit. This commit makes the replicate queue size configurable via a
cluster setting ReplicateQueueMaxSize, allowing incremental and backport-friendly
adjustments. Note that reducing the setting does not drop replicas appropirately;
future commits will address this behavior.
---
**kvserver: add TestReplicateQueueMaxSize**
This commit adds tests to (1) verify metric updates when replicas are dropped
from the queue, and (2) ensure the cluster setting for ReplicateQueueMaxSize
works correctly.
---
**kvserver: drop excess replicas when lowering ReplicateQueueMaxSize**
Previously, the ReplicateQueueMaxSize cluster setting allowed dynamic adjustment
of the replicate queue’s maximum size. However, decreasing this setting did not
properly drop excess replicas. This commit fixes that by removing replicas when
the queue’s max size is lowered.
---
**kvserver: rename ReplicateQueueDroppedDueToSize to ReplicateQueueFull**
This commit improves the clarity around the naming and description of the
metrics.
Co-authored-by: wenyihu6 <[email protected]>
0 commit comments