Milvus向量数据库修改配置后为何不生效

原创已于 2025-07-08 10:23:34 修改 · 416 阅读

8 ·

本内容遵循CC 4.0 BY-SA版权协议

GEO检测

标签

#milvus #数据库

于 2025-07-08 10:20:54 首次发布

Milvus 配置分类

目前按照功能不同，Milvus 的配置分为两大类：Milvus 内核配置和 Milvus 部署配置。

内核配置：milvus.yaml 我这里是custom_milvus.yaml

部署配置：docker-compose.yml 我这里是milvus-standalone-docker-compose.yml

部署模式：单机部署dock compost

版本：2.5.5

# docker ps -a
CONTAINER ID   IMAGE                                      COMMAND                  CREATED          STATUS                    PORTS                                              NAMES
fad521f68ef3   milvusdb/milvus:v2.5.5                     "/tini -- milvus run…"   12 minutes ago   Up 12 minutes (healthy)   0.0.0.0:9091->9091/tcp, 0.0.0.0:19530->19530/tcp   milvus-standalone
d63cffd8524c   minio/minio:RELEASE.2023-03-20T20-16-18Z   "/usr/bin/docker-ent…"   12 minutes ago   Up 12 minutes (healthy)   0.0.0.0:9000-9001->9000-9001/tcp                   milvus-minio
69fd85f12ced   quay.io/coreos/etcd:v3.5.5                 "etcd -advertise-cli…"   12 minutes ago   Up 12 minutes (healthy)   2379-2380/tcp                                      milvus-etcd
15637cecb1b9   zilliz/attu:latest                         "docker-entrypoint.s…"   3 days ago       Up 3 days                 0.0.0.0:8008->3000/tcp                             intelligent_fermat

尝试修改日志级别

首先获取当前日志级别：

# curl -X GET 1.4.196.12:9091/log/level
{"level":"info"}

(base) [root@196-12 milvus]# pwd
/database/app/milvus
(base) [root@db-hx-196-12 milvus]# cat milvus-standalone-docker-compose.yml

version: '3.5'

services:
  etcd:
    container_name: milvus-etcd
    image: quay.io/coreos/etcd:v3.5.5
    environment:
      - ETCD_AUTO_COMPACTION_MODE=revision
      - ETCD_AUTO_COMPACTION_RETENTION=1000
      - ETCD_QUOTA_BACKEND_BYTES=4294967296
      - ETCD_SNAPSHOT_COUNT=50000
    volumes:
      - ${DOCKER_VOLUME_DIRECTORY:-.}/volumes/etcd:/etcd
    command: etcd -advertise-client-urls=http://127.0.0.1:2379 -listen-client-urls http://0.0.0.0:2379 --data-dir /etcd
    healthcheck:
      test: ["CMD", "etcdctl", "endpoint", "health"]
      interval: 30s
      timeout: 20s
      retries: 3

  minio:
    container_name: milvus-minio
    image: minio/minio:RELEASE.2023-03-20T20-16-18Z
    environment:
      MINIO_ACCESS_KEY: minioadmin
      MINIO_SECRET_KEY: minioadmin
    ports:
      - "9001:9001"
      - "9000:9000"
    volumes:
      - ${DOCKER_VOLUME_DIRECTORY:-.}/volumes/minio:/minio_data
    command: minio server /minio_data --console-address ":9001"
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:9000/minio/health/live"]
      interval: 30s
      timeout: 20s
      retries: 3

  standalone:
    container_name: milvus-standalone
    image: milvusdb/milvus:v2.5.5
    command: ["milvus", "run", "standalone"]
    security_opt:
    - seccomp:unconfined
    environment:
      ETCD_ENDPOINTS: etcd:2379
      MINIO_ADDRESS: minio:9000
    volumes:
      - ${DOCKER_VOLUME_DIRECTORY:-.}/volumes/milvus:/var/lib/milvus
      - ./custom_milvus.yaml:/var/lib/milvus/conf/milvus.yaml
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:9091/healthz"]
      interval: 30s
      start_period: 90s
      timeout: 20s
      retries: 3
    ports:
      - "19530:19530"
      - "9091:9091"
    depends_on:
      - "etcd"
      - "minio"
    deploy:
      resources:
        limits:
          cpus: '30'
          memory: 70G
        reservations:
          memory: 8G
    ulimits:
      core: 1073741824


networks:
  default:
    name: milvus

修改配置，这里新增log部分配置
(base) [196-12 milvus]# vim custom_milvus.yaml

queryNode:
  gracefulTime: 5000
  flowGraph:
    maxQueueLength: 64


common:
  retryTimes: 10
  retryInterval: 1000
  default_consistency_level: "Bounded"


log:
  level: error  #info,warn,error,panic,fatal,debug
  file:
    rootPath:  
    maxSize:300 # MB
    maxAge: 10  # day
    maxBackups: 20

grpc:
  clientPool:
    maxSize: 1000  
    idleTimeout: 300s 

proxy:
  grpc:
    maxSendMsgSize: 512MB 
    maxRecvMsgSize: 512MB
  taskQueue:  
    maxTaskNum: 110  
    poolSize: 20   
    timeout: 10s
  loadBalancePolicy: roundRobin

memory:
  highMemUsageThreshold: 0.7  
  overloadThreshold: 0.85     
  enableTempMemoryRelease: true

重启生效：

docker compose -f /database/app/milvus/milvus-standalone-docker-compose.yml down
docker compose -f /database/app/milvus/milvus-standalone-docker-compose.yml up -d

再次查看log级别：
# curl -X GET 1.4.196.12:9091/log/level
{"level":"info"}

为什么没有生效？