Skip to content
Tagged articles

force merge

3 articles · Page 1 of 1
Shuge Unlimited
Shuge Unlimited
Oct 19, 2026 · Databases

Milvus 3.0 Segment Explosion: 12% Seal Threshold, 24h TTL, 16 Compaction Slots

This article dissects Milvus 3.0's default segment sealing behavior — 12% fill threshold, 24-hour TTL, and 16 compaction slots — explaining how sharding, large batches, and delete chains multiply segment counts, why compaction falls behind due to queue and slot bottlenecks, and the correct troubleshooting order: seal conditions first, compaction health second, manual force merge or clustering compaction last.

Configuration TuningL0 segmentsMilvus
0 likes · 21 min read
Milvus 3.0 Segment Explosion: 12% Seal Threshold, 24h TTL, 16 Compaction Slots
DevOps Coach
DevOps Coach
Oct 19, 2020 · Backend Development

Understanding Elasticsearch Segment Merging: When and How to Use Force Merge

This article explains what Elasticsearch segments are, why they are immutable, how segment merging works, its impact on resources and search performance, and provides practical configuration tips such as using force_merge, refresh_interval adjustments, and thread count settings.

ElasticsearchSegment Mergingforce merge
0 likes · 9 min read
Understanding Elasticsearch Segment Merging: When and How to Use Force Merge