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] just wrote 1.5G of data to the 16G memory milvus was forbidden to write #38706

Open
1 task done
wangting0128 opened this issue Dec 24, 2024 · 2 comments
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

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version:sunby-no_unlink-e76862d-20241217 
- 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-h4xxv

server:

NAME                                                              READY   STATUS                   RESTARTS         AGE     IP              NODE         NOMINATED NODE   READINESS GATES
wt-test-unlink-2-etcd-0                                           1/1     Running                  0                24h     10.104.25.198   4am-node30   <none>           <none>
wt-test-unlink-2-milvus-standalone-7857b5bbb5-thgsb               1/1     Running                  2 (24h ago)      24h     10.104.26.239   4am-node32   <none>           <none>
wt-test-unlink-2-minio-5c95dc8d69-tbs42                           1/1     Running                  0                24h     10.104.25.196   4am-node30   <none>           <none>
截屏2024-12-24 16 54 41

client log:
image

Expected Behavior

No response

Steps To Reproduce

1. create a collection with fields:
   - id: INT64, primary key
   - float_vector: 3dim
   - int64_1: INT64
2. build FLAT index on 'float_vector'
3. insert 3500m data <- inserted 60m data raised error `memory quota exceeded`

Milvus Log

No response

Anything else?

server config:

extraConfigFiles:
  user.yaml: |+
    dataCoord:
      segment:
        sealProportion: 1
    indexCoord:
      scheduler:
        interval: 1
    queryNode:
      cache:
        warmup: sync
      mmap:
        vectorField: true
        vectorIndex: true
        scalarField: true
        scalarIndex: true
standalone:
  resources:
    limits:
      cpu: '2.0'
      memory: 16Gi
    requests:
      cpu: '1.0'
      memory: 10Gi
  nodeSelector:
    node-role/nvme: 'true'
    kubernetes.io/hostname: 4am-node32

client config:

{
     "dataset_params": {
          "metric_type": "L2",
          "dim": 3,
          "dataset_name": "local",
          "dataset_size": "3500m",
          "ni_per": 1000000
     },
     "collection_params": {
          "shards_num": 1,
          "other_fields": [
               "int64_1"
          ],
          "collection_name": "scene_int64_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": [
                         "int64_1"
                    ],
                    "limit": 10,
                    "timeout": 600,
                    "random_data": true,
                    "random_count": 10,
                    "random_range": [
                         0,
                         35000000
                    ],
                    "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 24, 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 added this to the 2.5.1 milestone Dec 25, 2024
@yanliang567 yanliang567 removed their assignment Dec 25, 2024
@xiaofan-luan
Copy link
Collaborator

/assign @MrPresent-Han
please help on it

@MrPresent-Han
Copy link
Contributor

I will handle this

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

5 participants