[Bug]: milvus container exit after having 100 collections loaded

[shanghaikid]

Is there an existing issue for this?

• I have searched the existing issues

Environment

- Milvus version: v2.5.10 
- Deployment mode(standalone or cluster):standalone

Current Behavior

the container exit

Expected Behavior

No response

Steps To Reproduce

1. create 100 collections(id, vector(dim4), autoId: false, dynamic field enabled)
2. insert 2k rows into each collection
3. create index(autoindex)
4. load collection
5. call ShowCollections with type = 1 or type 0 multiple times. 
6. the container exit

Milvus Log

milvus.container.log.zip

Anything else?

No response

[yanliang567]

I did not find any suspected errors in the logs, but many growing segments. I guess it was an OOM? could you please retry without loading or with mmap enabled? @shanghaikid

[shanghaikid]

yes, it's OOM. I just assign 2GB to the milvus container. should I close the ticket ? or should milvus tell me my memory is not enough.

[xiaofan-luan]

usually you should get memory not enough error.
but the memory control might not be very accurate under small dim and less memory.

Mark this as low priority

[yanliang567]

i will close this issue, lets track the oom issue in the other issues