Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: [benchmark][retrieve] milvus(enabled all mmap) OOM when loading a collection with array(varchar) field #38736

Open
1 task done
wangting0128 opened this issue Dec 25, 2024 · 1 comment
Assignees
Labels
kind/bug Issues or changes related a bug triage/accepted Indicates an issue or PR is ready to be actively worked on.
Milestone

Comments

@wangting0128
Copy link
Contributor

wangting0128 commented Dec 25, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version:sunby-no_unlink-ceed4f7-20241224
- Deployment mode(standalone or cluster):standalone
- MQ type(rocksmq, pulsar or kafka):rocksmq    
- SDK version(e.g. pymilvus v2.0.0rc2):2.5.0rc124
- OS(Ubuntu or CentOS): 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

argo task: fouramf-w894f

server:

NAME                                                              READY   STATUS                   RESTARTS        AGE     IP              NODE         NOMINATED NODE   READINESS GATES
wt-test-unlink-etcd-0                                             1/1     Running                  0               7d19h   10.104.26.150   4am-node32   <none>           <none>
wt-test-unlink-milvus-standalone-5f8b7b6b95-g64sj                 1/1     Running                  4 (15h ago)     24h     10.104.26.176   4am-node32   <none>           <none>
wt-test-unlink-minio-67b75cfbf4-dk5ht                             1/1     Running                  0               7d19h   10.104.26.152   4am-node32   <none>           <none>
截屏2024-12-25 11 34 08 截屏2024-12-25 11 35 56 截屏2024-12-25 11 36 17

client log:
截屏2024-12-25 11 38 25

Expected Behavior

No response

Steps To Reproduce

  1. create a collection with fields: 'id'(INT64, primary key), 'float_vector'(3dim), 'array_varchar_1'
  2. build FLAT index on field float_vector
  3. insert 900m data
  4. flush collection
  5. load collection <- milvus OOM

Milvus Log

No response

Anything else?

client config:

{
     "dataset_params": {
          "metric_type": "L2",
          "dim": 3,
          "dataset_name": "local",
          "dataset_size": "900m",
          "ni_per": 50000,
          "scalars_params": {
               "array_varchar_1": {
                    "params": {
                         "max_length": 100,
                         "max_capacity": 10
                    }
               }
          }
     },
     "collection_params": {
          "shards_num": 1,
          "other_fields": [
               "array_varchar_1"
          ],
          "collection_name": "scene_array_varchar_1"
     },
     "index_params": {
          "index_type": "FLAT",
          "index_param": {}
     },
     "concurrent_params": {
          "concurrent_number": [
               10,
               100
          ],
          "during_time": "30m",
          "interval": 20
     },
     "concurrent_tasks": [
          {
               "type": "query",
               "weight": 1,
               "params": {
                    "expr": "",
                    "output_fields": [
                         "array_varchar_1"
                    ],
                    "limit": 10,
                    "timeout": 600,
                    "random_data": true,
                    "random_count": 10,
                    "random_range": [
                         0,
                         900000000
                    ],
                    "field_name": "id",
                    "field_type": "int64"
               }
          }
     ]
}
@wangting0128 wangting0128 added kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Dec 25, 2024
@yanliang567 yanliang567 added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Dec 25, 2024
@yanliang567 yanliang567 removed their assignment Dec 25, 2024
@yanliang567 yanliang567 added this to the 2.5.1 milestone Dec 25, 2024
@MrPresent-Han
Copy link
Contributor

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Issues or changes related a bug triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

4 participants