wayblink
wayblink
@sumanthhuddar As @yanliang567 mentioned, it is currently expected. We will think about adding policy to split the large segments to smaller ones. Clustering compaction can compact segments to smaller size....
@zhangzf875 It may caused by the port of minio is not exposed outside the docker. Need to edit the docker yaml to expose the ports
暂时这方面需求很弱 没有计划去做，如果有强烈需求，欢迎实现贡献给我们哈
> --restore_index -n Please run ```./milvus-backup check``` and see the output. Have you check whether the path 'backup/firstbackup4/meta/backup_meta.json' exists? What is your S3 provider? I guess it may related to...
> ``` > [root backup]# ./milvus-backup check > 0.4.24 (Built on 2024-09-20T02:08:15Z from Git SHA 290692046dd95b1140d3c0d376cf7a5e7ade7971) > config:backup.yaml > [2024/09/27 09:42:34.550 +08:00] [INFO] [logutil/logutil.go:165] ["Log directory"] [configDir=] > [2024/09/27 09:42:34.550...
@suyestyle mentioned above. The config may be wrong. No binlog data is backuped actually. Please config the minio part the same as your milvus cluster.
> I modified the configuration according to the actual situation of my environment by referring to the official configuration. If there are errors in the configuration file, please help me...
> Now the backup is reporting an error. > > ``` > 0.4.24 (Built on 2024-09-20T02:08:15Z from Git SHA 290692046dd95b1140d3c0d376cf7a5e7ade7971) > config:backup.yaml > [2024/10/15 16:34:21.328 +08:00] [INFO] [logutil/logutil.go:165] ["Log directory"]...