kdrant-core/dev.kdrant.model/QuotaConfig

QuotaConfig

@Serializable

data class QuotaConfig(val enabled: Boolean? = null, val maxResidentMemoryPercent: Int? = null, val maxDiskUsagePercent: Int? = null, val releaseMarginPercent: Int? = null)

Cluster-wide limits on node resources, introduced in Qdrant 1.19 to replace the per-collection ceilings that strict mode carried.

An unset limit is not a limit of zero: it means the resource is not capped. Nothing is enforced at all while enabled is false, which is the default, so a config written with limits and left disabled is a config that does nothing.

Constructors

QuotaConfig

constructor(enabled: Boolean? = null, maxResidentMemoryPercent: Int? = null, maxDiskUsagePercent: Int? = null, releaseMarginPercent: Int? = null)

Properties

enabled

@SerialName(value = "enabled")

val enabled: Boolean?

Whether the limits below are enforced. A quota that is off refuses nothing.

maxDiskUsagePercent

@SerialName(value = "max_disk_usage_percent")

val maxDiskUsagePercent: Int?

Refuse disk-consuming updates once the storage filesystem is this full.

maxResidentMemoryPercent

@SerialName(value = "max_resident_memory_percent")

val maxResidentMemoryPercent: Int?

Refuse memory-consuming updates once the process's resident memory reaches this percentage of the memory available to it, which is the cgroup limit where one applies rather than the machine's.

releaseMarginPercent

@SerialName(value = "release_margin_percent")

val releaseMarginPercent: Int?

How far below a limit a resource has to fall before the node accepts work again.