Skip to content

Backup fails with Milvus master due to new parquet-based binlog path format #974

@zhuwenxing

Description

@zhuwenxing

Summary

Milvus backup fails when running against Milvus master (nightly build master-20260309-bc9b741) because the insert log path format has changed to a new parquet-based format that the current path parser does not recognize.

Error

Error: create: execute task: backup: run collection task: backup: execute collection strategy: backup: execute dml task backup: wait task backup: execute task backup: execute dml task backup: get segments backup: get segment backup: get segment info backup: list insert logs backup: parse log path mpath: log path files/insert_log/464794107665636903/464794107665636904/464794107665786973/_data/0_010464ea-7aa4-47da-9722-81795c1f3edc.parquet is not match the pattern

Root Cause

The current insert log path regex in internal/storage/mpath/path.go:228 expects:

insert_log/{collectionID}/{partitionID}/{segmentID}/{fieldID}/{logID}

But Milvus master now produces paths like:

insert_log/{collectionID}/{partitionID}/{segmentID}/_data/{index}_{uuid}.parquet

The _data segment and {index}_{uuid}.parquet filename do not match the existing pattern (\d+)/(\d+).

Affected CI Jobs

All nightly CI jobs using master-latest are failing at the Backup step:

  • Backup and restore secondary (master-latest)
  • Backup and restore with rbac config (helm, standalone, master-latest)
  • Backup and restore after upgrade (docker-compose, standalone, standalone, 2.5-latest, master-latest)
  • Backup and restore cli (docker-compose, standalone, standalone, master-latest)

CI run: https://github.com/zilliztech/milvus-backup/actions/runs/22846884679?pr=973

Expected Behavior

milvus-backup should be able to parse the new parquet-based binlog path format and successfully back up collections from Milvus master.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions