[Bug]: Create collection gets error: Broker: Invalid replication factor

[ThreadDao]

Is there an existing issue for this?

• [X] I have searched the existing issues

Environment

- Milvus version: 2.3-20240423-deda656d-amd64
- Deployment mode(standalone or cluster): standalone
- MQ type(rocksmq, pulsar or kafka): kafka    
- SDK version(e.g. pymilvus v2.0.0rc2): pymilvus 2.3.8rc5
- OS(Ubuntu or CentOS): 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

• argo workflow: https://argo-workflows.zilliz.cc/archived-workflows/qa/d0c02725-4b23-47b4-a7d4-b0a36ac096ef?nodeId=zong-chaos-standalone-233-1713895200

1. deploy standalone with Kafka mq by milvus-operator and wait healthy

[2024-04-23 18:11:25,676 -  INFO - fouram]: [wait_for_healthy] Instance:zong-chaos-standalone-233 is healthy. (operator_client.py:189)
[2024-04-23 18:11:26,674 -  INFO - fouram]: [get_pods] pod details of release(zong-chaos-standalone-233):  (operator_client.py:306)
[2024-04-23 18:11:26,674 -  INFO - fouram]: 
NAME                                                             STATUS      RESTARTS     AGE     IP                NODE           
zong-chaos-standalone-233-milvus-standalone-7d6b88d478-6v92t     Running     0            1m      10.104.5.53       4am-node12     
zong-chaos-standalone-233-etcd-0                                 Running     0            4m      10.104.32.20      4am-node39     
zong-chaos-standalone-233-kafka-0                                Running     1            4m      10.104.32.21      4am-node39     
zong-chaos-standalone-233-kafka-1                                Running     0            4m      10.104.26.164     4am-node32     
zong-chaos-standalone-233-kafka-2                                Running     1            4m      10.104.15.7       4am-node20     
zong-chaos-standalone-233-kafka-zookeeper-0                      Running     0            4m      10.104.32.18      4am-node39     
zong-chaos-standalone-233-kafka-zookeeper-1                      Running     0            4m      10.104.23.165     4am-node27     
zong-chaos-standalone-233-kafka-zookeeper-2                      Running     0            4m      10.104.30.92      4am-node38     
zong-chaos-standalone-233-minio-54664b8696-z8nxj                 Running     0            4m      10.104.32.19      4am-node39     
 (common_func.py:407)

2. create collection and gets error:

[2024-04-23 18:13:47,058 -  INFO - fouram]: [Base] Connection params: {'alias': 'default', 'host': 'zong-chaos-standalone-233-milvus.qa-milvus', 'port': '19530', 'uri': '', 'secure': False, 'user': '', 'password': '', 'token': '', 'db_name': ''} (base.py:237)
[2024-04-23 18:13:47,245 -  INFO - fouram]: [Base] Start clean all collections [] (base.py:286)
[2024-04-23 18:13:47,247 -  INFO - fouram]: [Base] Create collection fouram_5ThPw2pp (base.py:270)
[2024-04-23 18:13:47,265 - ERROR - fouram]: RPC error: [create_collection], <MilvusException: (code=65535, message=Broker: Invalid replication factor)>, <Time:{'RPC start': '2024-04-23 18:13:47.249024', 'RPC error': '2024-04-23 18:13:47.265123'}> (decorators.py:139)
[2024-04-23 18:13:47,266 - ERROR - fouram]: (api_response) : [Collection] <MilvusException: (code=65535, message=Broker: Invalid replication factor)>, [requestId: 3a5d8012-019d-11ef-8d5f-9a15d6d3fee7] (api_request.py:57)
[2024-04-23 18:13:47,266 - ERROR - fouram]: [CheckFunc] init_collection request check failed, response:<MilvusException: (code=65535, message=Broker: Invalid replication factor)> (func_check.py:54)

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response

[xiaofan-luan]

/assign @chyezh

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. Rotten issues close after 30d of inactivity. Reopen the issue with /reopen.

[yanliang567]

any updates ? @chyezh @ThreadDao

[chyezh]

@yanliang567 @ThreadDao it's not a issue of milvus. When start the cluster, milvus don't check the kafka broker and topic status. And topic of kafka is lazy created. So when create collection, there's not enough broker to hold created topic. create collection got a error like that.

So I think that the issue can be closed without any change.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. Rotten issues close after 30d of inactivity. Reopen the issue with /reopen.