langgenius / dify

Dify is an open-source LLM app development platform. Dify's intuitive interface combines AI workflow, RAG pipeline, agent capabilities, model management, observability features and more, letting you quickly go from prototype to production.
https://dify.ai
Other
48.49k stars 6.93k forks source link

0.9.x Milvus Index Error #9509

Open yfge opened 5 hours ago

yfge commented 5 hours ago

Self Checks

Dify version

0.9.2

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

Hi,I've upgrade dify to 0.9.2,and I found the timeout error of Milvus.

[2024-10-20 04:42:37,979: ERROR/MainProcess] Failed to create collection: Vector_index_465ed6b5_b0c1_4996_883c_bc6a6e072970_Node
[2024-10-20 04:43:07,981: ERROR/MainProcess] RPC error: [create_collection], <MilvusException: (code=65535, message=message send timeout: TimeoutError)>, <Time:{'RPC start': '2024-10-20 04:38:07.961715', 'RPC error': '2024-10-20 04:43:07.981528'}>

✔️ Expected Behavior

Index success before upgrade

❌ Actual Behavior

[2024-10-20 04:42:37,979: ERROR/MainProcess] Failed to create collection: Vector_index_465ed6b5_b0c1_4996_883c_bc6a6e072970_Node
[2024-10-20 04:43:07,981: ERROR/MainProcess] RPC error: [create_collection], <MilvusException: (code=65535, message=message send timeout: TimeoutError)>, <Time:{'RPC start': '2024-10-20 04:38:07.961715', 'RPC error': '2024-10-20 04:43:07.981528'}>
dosubot[bot] commented 5 hours ago

Hello @yfge! I'm here to help with any bugs, questions, or contributions you have for Dify. Just let me know how I can assist you!

The error you're encountering seems to be related to a timeout issue when creating a collection in Milvus after upgrading to Dify version 0.9.2. This could be due to the default timeout settings for RPC calls in the Dify codebase. Unfortunately, I couldn't find specific information on how to adjust these timeout settings in the available documentation.

However, you might want to check the configuration files or environment variables related to Milvus and Dify to see if there are any timeout settings that can be adjusted. Additionally, ensure that your Milvus server is running properly and that there are no network issues that could be causing the timeout.

If the problem persists, consider looking into the Milvus logs for more detailed error messages that might provide further insights into the issue.

To continue talking to Dosu, mention @dosu.

yfge commented 5 hours ago

I have configure the MILVUS_URI before the update