Stand-alone deployment fails to dump access logs to a file when configured for it

[zeeIBM]

Environment: Standalone on docker
Version: 2.4

When configured for dumping access logs to a file. The access logs are not being generated in the file. I even manually created the directory and file with open permissions to it.

It did not work. My config in milvus.yaml are:

accessLog:
    enable: true # if use access log
    minioEnable: false # if upload sealed access log file to minio
    localPath: /tmp/milvus_access/
    filename: "access.log"  # Log filename, leave empty to use stdout.
    maxSize: 64 # Max size for a single file, in MB.
    cacheSize: 10240 # Size of log of memory cache, in B
    rotatedTime: 0 # Max time for single access log file in seconds
    remotePath: access_log/ # File path in minIO
    remoteMaxTime: 0 # Max time for log file in minIO, in hours
    formatters:
      base:
        format: "[ACCESS] [trace id: $trace_id] [database: $database_name] [$time_now] <$user_addr : $user_name> $method_name [method status: $method_status] [collection name: $collection_name] [response size: $response_size] [query expression: $method_expr] [error code: $error_code] [error msg: $error_msg]"

[aoiasd]

Can not reproduce in 2.4.7

May caused by cacheSize set as 10240(10KB), means log won't write to file till log data in memory size large than 10KB, and will loss some log if program died.

[yhmo]

Follow these steps:

1. set milvus.yaml

accessLog:
    enable: true
    localPath: /tmp/milvus_accesslog
    filename: "access.log"

2. docker compose up -d
3. docker ps
4. docker exec -it [milvus_container_id] bash
5. cd /tmp/milvus_accesslog
6. cat access.log
   

[zeeIBM]

Yes I wanted the access log file to be inside the container not on the host machine.

I demoed the issue to @xiaofan-luan in milvus 2.4.4 with cache size set to zero.

I will try in milvus 2.4.7 as suggested.

cc: @xiaofan-luan

[xiaofan-luan]

Yes I wanted the access log file to be inside the container not on the host machine.

I demoed the issue to @xiaofan-luan in milvus 2.4.4 with cache size set to zero.

I will try in milvus 2.4.7 as suggested.

cc: @xiaofan-luan

did you try with the config yhmo suggested?>

accessLog:
enable: true
localPath: /tmp/milvus_accesslog
filename: "access.log"

[xiaofan-luan]

it seems to be working on milvus 2.4.16, as yhmo showed

[yanliang567]

it seems to be working on milvus 2.4.4 for me. I ran a few tests against the milvus and logged into the milvus pod to check the access log.
I deploy milvus with operator with the config below

[zeeIBM]

@yanliang567 My setup was standalone on docker image that i deployed using: https://milvus.io/docs/install_standalone-docker.md

could it be different than the one you have in a cluster pod?

[zeeIBM]

I upgraded the version to miluvs 2.5_beta in stand alone setup. Now I am able to see accessLogs to the configured file