Database / Milvus Vector database Interview questions
Explain the internal working of Milvus's segment sealing and index-building pipeline?
Turning freshly written data into a fully-optimized, searchable index involves a coordinated handoff between several components, each responsible for one stage of the pipeline.
Crucially, the sealed segment remains fully queryable via brute-force scan throughout the index-building process; index building runs asynchronously and doesn't block reads, so a slow or even temporarily failed index build doesn't make that segment's data unavailable, it just means queries against it are less optimized (falling back to brute-force) until the proper index is ready or the build is retried.
This asynchronous, non-blocking design is deliberate: it decouples data durability and searchability (which need to happen quickly, as covered by growing/sealed segment search) from index optimization (which is comparatively expensive and doesn't need to happen synchronously with every write) letting Milvus prioritize write availability and basic search correctness over immediately having every byte of data behind a fully-tuned index.
More Related questions...