d500dc90d6 enhance: [poc_2.6.17] de-synchronize and rate-limit delete-triggered single compaction (#51434)
issue: #51094 (ported from #51096, targeting the poc_2.6.17 production
branch where the incident occurred)

### What

Segments created in the same batch (bulk import, DR initial sync,
restore) accumulate deltalogs at nearly the same rate, so they cross the
single-compaction hard thresholds almost simultaneously. The result is a
synchronized rewrite avalanche: in a production incident, ~1,400
segments became eligible within ~36 hours and the cluster rewrote
multiple TB against a rate-limited object store, degrading queries for
days.

Two independent, individually-disableable, refreshable mechanisms:

1. **Deterministic per-segment threshold jitter**
(`dataCoord.compaction.single.thresholdJitter`, default 0.25). Each
segment gets a stable multiplier in `[1, 1+J]` (splitmix64 hash of
segment ID — no persisted state, consistent across restarts/nodes)
applied to every accumulation dimension (deltalog count/size,
deleted-rows ratio, expired-entities ratio/size). Applies to **all**
single-compaction trigger axes and spreads a cohort's crossing times.
2. **Token-bucket admission at plan generation**
(`dataCoord.compaction.single.rateLimitTokens` / `rateLimitInterval`,
default 256 per 60s) for **delete-accumulation candidates only**,
dirtiest-first, with a jittered bounded-deferral escape.

### Scope of each mechanism (precise guarantees)

- The **token-bucket rate ceiling applies to delete accumulation only.**
Its dirtiest-first ordering and its bounded-deferral escape both use a
*normalized delete pressure* = `max` over the three delete axes
(deltalog count, deleted-rows ratio, delete-log size) of `actual /
threshold`, so a segment triggered by any single axis (e.g. large
varchar-PK deletes concentrated in a few files) is ordered and bounded
on that axis — not only on file count.
- **Expiry accumulation, strict age-based TTL, and index rebuild bypass
admission** (they are retention / correctness obligations that must not
be paced behind a delete backlog). They are **de-synchronized by jitter
only**, not rate-capped. A TTL cliff is therefore smeared by jitter, not
converted into a token-bucket-paced stream.
- The bounded-deferral **escape is itself jittered** (`pressure >= 4x`
scaled by the segment's jitter multiplier) and does not consume a token,
so a deferred count-triggered cohort does not re-synchronize at the `4x`
threshold and avalanche through the bypass together. The same jitter
means a threshold config *decrease* raises pressure into a per-segment
spread of escape points rather than releasing the cohort in one round.
- An axis whose threshold is non-positive is skipped, so a misconfigured
(`<= 0`) threshold disables that axis rather than turning the escape
into a free bypass.
- `thresholdJitter=0` plus `rateLimitTokens=0` restore exact legacy
behavior; force/manual compaction bypasses admission.

### Adversarial-review fixes folded in (three rounds on #51096)

- **Starvation of non-delete reasons** — only delete accumulation is
admission-gated; expiry accumulation, strict age-TTL and index rebuild
bypass pacing.
- **Bounded deferral on every delete axis** (not just file count) via
the normalized-pressure escape; dirtiest-first ordering likewise covers
all axes.
- **Jittered escape** so a deferred count-triggered cohort cannot
re-synchronize and avalanche through the bypass.
- **Sub-one token budget soft-deadlock** — a positive `rateLimitTokens`
below 1 clamps to 1.
- **Non-positive threshold** no longer disables pacing (per-axis skip).
- **Throttle-warning masking** — the sustained-throttle counter is
cleared only when the bucket has genuinely refilled.
- **Tokens vs backpressure** — both the L1 trigger and the L2 policy
refund tokens for admission-gated segments whose plans are dropped
before enqueue.

The single shared bucket is intentional: it bounds *aggregate* rewrite
load against the object store (which is source-agnostic), and refills
every round; per-caller buckets would multiply the aggregate ceiling by
the caller count and defeat the protection. Sustained one-sided
saturation is surfaced by the throttle warning.

### Test plan

- New `compaction_admission_test.go`: multiplier determinism / range /
zero-jitter disable; disabled-bucket passthrough, dirtiest-first
limiting, jittered escape bypass, token refill with injected clock; plus
dedicated cases for each review fix (sub-one budget, delete-size-axis
reaches the escape, non-positive threshold still paces, refund,
throttle-counter survival on a drained bucket, reason classification).
- Existing `Test_compactionTrigger_*`,
`TestSingleCompactionPolicySuite`, `TestCompactionTriggerManager` pass;
two cases asserting the exact legacy `201 vs 200` deltalog boundary pin
`thresholdJitter=0`.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Signed-off-by: zhenshan.cao <caozhenshan007@gmail.com>
Co-authored-by: zhenshan.cao <caozhenshan007@gmail.com>
2026-07-15 19:43:45 -07:00
2023-03-02 15:55:49 +08:00
2025-07-29 12:05:43 +08:00
2021-04-21 14:04:22 +08:00
2025-07-21 12:00:46 +00:00
2025-07-21 12:00:46 +00:00
2023-09-21 09:45:27 +08:00

milvus banner
license docker-pull-count fully-managed-milvus fully-managed-milvus tutorials discord twitter

What is Milvus?

🐦 Milvus is a high-performance vector database built for scale. It powers AI applications by efficiently organizing and searching vast amounts of unstructured data, such as text, images, and multi-modal information.

🧑‍💻 Written in Go and C++, Milvus implements hardware accelaration for CPU/GPU to achieve best-in-class vector search performance. Thanks to its fully-distributed and K8s-native architecture, Milvus can scale horizontally, handle tens of thousands of search queries on billions of vectors, and keep data fresh with real-time streaming updates. Milvus also supports Standalone mode for single machine deployment. Milvus Lite is a lightweight version good for quickstart in python with pip install.

Want to use Milvus with zero setup? Try out Zilliz Cloud ☁️ for free. Milvus is available as a fully managed service on Zilliz Cloud, with Serverless, Dedicated and BYOC options available.

For questions about how to use Milvus, join the community on Discord to get help. For reporting problems, file bugs and feature requests in GitHub Issues or ask in Discussions.

The Milvus open-source project is under LF AI & Data Foundation, distributed with Apache 2.0 License, with Zilliz as its major contributor.

Quickstart

$ pip install -U pymilvus

This installs pymilvus, the Python SDK for Milvus. Use MilvusClient to create a client:

from pymilvus import MilvusClient
  • pymilvus also includes Milvus Lite for quickstart. To create a local vector database, simply instantiate a client with a local file name for persisting data:

    client = MilvusClient("milvus_demo.db")
    
  • You can also specify the credentials to connect to your deployed Milvus server or Zilliz Cloud:

    client = MilvusClient(
      uri="<endpoint_of_self_hosted_milvus_or_zilliz_cloud>",
      token="<username_and_password_or_zilliz_cloud_api_key>")
    

With the client, you can create collection:

client.create_collection(
    collection_name="demo_collection",
    dimension=768,  # The vectors we will use in this demo have 768 dimensions
)

Ingest data:

res = client.insert(collection_name="demo_collection", data=data)

Perform vector search:

query_vectors = embedding_fn.encode_queries(["Who is Alan Turing?", "What is AI?"])
res = client.search(
    collection_name="demo_collection",  # target collection
    data=query_vectors,  # a list of one or more query vectors, supports batch
    limit=2,  # how many results to return (topK)
    output_fields=["vector", "text", "subject"],  # what fields to return
)

Why Milvus

Milvus is designed to handle vector search at scale. It stores vectors, which are learned representations of unstructured data, together with other scalar data types such as integers, strings, and JSON objects. Users can conduct efficient vector search with metadata filtering or hybrid search. Here are why developers choose Milvus as the vector database for AI applications:

High Performance at Scale and High Availability

  • Milvus features a distributed architecture that separates compute and storage. Milvus can horizontally scale and adapt to diverse traffic patterns, achieving optimal performance by independently increasing query nodes for read-heavy workload and data node for write-heavy workload. The stateless microservices on K8s allow quick recovery from failure, ensuring high availability. The support for replicas further enhances fault tolerance and throughput by loading data segments on multiple query nodes. See benchmark for performance comparison.

Support for Various Vector Index Types and Hardware Acceleration

  • Milvus separates the system and core vector search engine, allowing it to support all major vector index types that are optimized for different scenarios, including HNSW, IVF, FLAT (brute-force), SCANN, and DiskANN, with quantization-based variations and mmap. Milvus optimizes vector search for advanced features such as metadata filtering and range search. Additionally, Milvus implements hardware acceleration to enhance vector search performance and supports GPU indexing, such as NVIDIA's CAGRA.

Flexible Multi-tenancy and Hot/Cold Storage

  • Milvus supports multi-tenancy through isolation at database, collection, partition, or partition key level. The flexible strategies allow a single cluster to handle hundreds to millions of tenants, also ensures optimized search performance and flexible access control. Milvus enhances cost-effectiveness with hot/cold storage. Frequently accessed hot data can be stored in memory or on SSDs for better performance, while less-accessed cold data is kept on slower, cost-effective storage. This mechanism can significantly reduce costs while maintaining high performance for critical tasks.

Sparse Vector for Full Text Search and Hybrid Search

  • In addition to semantic search through dense vector, Milvus also natively supports full text search with BM25 as well as learned sparse embedding such as SPLADE and BGE-M3. Users can store sparse vector and dense vector in the same collection, and define functions to rerank results from multiple search requests. See examples of Hybrid Search with semantic search + full text search.

Data Security and Fine-grain Access Control

  • Milvus ensures data security by implementing mandatory user authentication, TLS encryption, and Role-Based Access Control (RBAC). User authentication ensures that only authorized users with valid credentials can access the database, while TLS encryption secures all communications within the network. Additionally, RBAC allows for fine-grained access control by assigning specific permissions to users based on their roles. These features make Milvus a robust and secure choice for enterprise applications, protecting sensitive data from unauthorized access and potential breaches.

Milvus is trusted by AI developers to build applications such as text and image search, Retrieval-Augmented Generation (RAG), and recommendation systems. Milvus powers many mission-critical business for startups and enterprises.

Demos and Tutorials

Here is a selection of demos and tutorials to show how to build various types of AI applications made with Milvus:

You can explore a comprehensive Tutorials Overview covering topics such as Retrieval-Augmented Generation (RAG), Semantic Search, Hybrid Search, Question Answering, Recommendation Systems, and various quick-start guides. These resources are designed to help you get started quickly and efficiently.

Tutorial Use Case Related Milvus Features
Build RAG with Milvus RAG vector search
Advanced RAG Optimizations RAG vector search, full text search
Full Text Search with Milvus Text Search full text search
Hybrid Search with Milvus Hybrid Search hybrid search, multi vector, dense embedding, sparse embedding
Image Search with Milvus Semantic Search vector search, dynamic field
Multimodal Search using Multi Vectors Semantic Search multi vector, hybrid search
Movie Recommendation with Milvus Recommendation System vector search
Graph RAG with Milvus RAG graph search
Contextual Retrieval with Milvus Quickstart vector search
Vector Visualization Quickstart vector search
HDBSCAN Clustering with Milvus Quickstart vector search
Use ColPali for Multi-Modal Retrieval with Milvus Quickstart vector search
Image Search RAG Drug Discovery

Ecosystem and Integration

Milvus integrates with a comprehensive suite of AI development tools, such as LangChain, LlamaIndex, OpenAI and HuggingFace, making it an ideal vector store for GenAI applications such as Retrieval-Augmented Generation (RAG). Milvus works with both open-source embedding models and embedding service, in text, image and video modalities. Milvus also provides a convenient util pymilvus[model], users can use the simple wrapper code to transform unstructured data into vector embeddings and leverage reranking models for optimized search results. The Milvus ecosystem also includes Attu for GUI-based administration, Birdwatcher for system debugging, Prometheus/Grafana for monitoring, Milvus CDC for data synchronization, VTS for data migration and data connectors for Spark, Kafka, Fivetran, and Airbyte to build search pipelines.

Check out https://milvus.io/docs/integrations_overview.md for more details.

Documentation

For guidance on installation, usage, deployment, and administration, check out Milvus Docs. For technical milestones and enhancement proposals, check out issues on GitHub.

Contributing

The Milvus open-source project accepts contribution from everyone. See Guidelines for Contributing for details on submitting patches and the development workflow. See our community repository to learn about project governance and access more community resources.

Build Milvus from Source Code

Requirements:

  • Linux systems (Ubuntu 20.04 or later recommended):

    go: >= 1.21
    cmake: >= 3.26.4
    gcc: 9.5
    python: > 3.8 and  <= 3.11
    
  • MacOS systems with x86_64 (Big Sur 11.5 or later recommended):

    go: >= 1.21
    cmake: >= 3.26.4
    llvm: >= 15
    python: > 3.8 and  <= 3.11
    
  • MacOS systems with Apple Silicon (Monterey 12.0.1 or later recommended):

    go: >= 1.21 (Arch=ARM64)
    cmake: >= 3.26.4
    llvm: >= 15
    python: > 3.8 and  <= 3.11
    

Clone Milvus repo and build.

# Clone github repository.
$ git clone https://github.com/milvus-io/milvus.git

# Install third-party dependencies.
$ cd milvus/
$ ./scripts/install_deps.sh

# Compile Milvus.
$ make

For full instructions, see developer's documentation.

Community

Join the Milvus community on Discord to share your suggestions, advice, and questions with our engineering team.

To learn latest news about Milvus, follow us on social media:

You can also check out our FAQ page to discover solutions or answers to your issues or questions, and subscribe to Milvus mailing lists:

Reference

Reference to cite when you use Milvus in a research paper:

@inproceedings{2021milvus,
  title={Milvus: A Purpose-Built Vector Data Management System},
  author={Wang, Jianguo and Yi, Xiaomeng and Guo, Rentong and Jin, Hai and Xu, Peng and Li, Shengjun and Wang, Xiangyu and Guo, Xiangzhou and Li, Chengming and Xu, Xiaohai and others},
  booktitle={Proceedings of the 2021 International Conference on Management of Data},
  pages={2614--2627},
  year={2021}
}

@article{2022manu,
  title={Manu: a cloud native vector database management system},
  author={Guo, Rentong and Luan, Xiaofan and Xiang, Long and Yan, Xiao and Yi, Xiaomeng and Luo, Jigao and Cheng, Qianya and Xu, Weizhi and Luo, Jiarui and Liu, Frank and others},
  journal={Proceedings of the VLDB Endowment},
  volume={15},
  number={12},
  pages={3548--3561},
  year={2022},
  publisher={VLDB Endowment}
}


Languages
Go 57.9%
Python 21%
C++ 19.6%
Shell 0.5%
Groovy 0.3%
Other 0.5%