After using the Jina embedding model, when processing the knowledge base, it would fully occupy the CPU performance and throw a 'NoneType' error

[car9797]

Self Checks

• [X] I have searched for existing issues search for existing issues, including closed ones.
• [X] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [X] Pleas do not modify this template :) and fill in all the required fields.

Dify version

0.5.8

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

"After using the Jina embedding model, when processing the knowledge base, it would fully occupy the CPU performance and throw a 'NoneType' error."

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

[dosubot[bot]]

Hey there, @car9797! 👋 I'm Dosu, your friendly neighborhood bot here to assist with bug squashing, answering queries, and helping you contribute while you wait for a human maintainer to swing by. Let's take a closer look at what's gnawing at your Jina embedding model together. Expect a full answer from me shortly! 🤖

[crazywoola]

@car9797 Do you have enough keys to complete this index job?

[dosubot[bot]]

Based on the information you've provided, it seems like the 'NoneType' error and the CPU spike could be related to the Jina embedding model or the Dify setup. However, without the exact error message, it's hard to pinpoint the exact issue. If you could provide the exact 'NoneType' error message, it would be easier to diagnose the problem.

As for the system requirements, Dify version 0.5.8 requires at least a 2 core CPU and 4GB of RAM as per the README.md. If your system meets these requirements, it should be able to handle the index job. However, depending on the size of your knowledge base and the specific Jina embedding model you're using, you might need more resources.

Regarding the keys, it's not clear what you mean by "having enough keys to complete the index job". If you're referring to API keys or similar, those would be specific to the services you're using and wouldn't typically affect CPU usage or cause a 'NoneType' error. If you're referring to something else, could you please clarify?

Lastly, I noticed that your Docker setup includes multiple services, including an API service, a worker service, a frontend web application, a PostgreSQL database, a Redis cache, a Weaviate vector store, and an Nginx reverse proxy. If any of these services are misconfigured or not working correctly, they could potentially cause issues with the index job. You might want to check the logs for each service to see if there are any errors or warnings.

I hope this helps! If you have any more information or if there's anything else you're unsure about, please let me know.

Sources

• docker/docker-compose.yaml
• README.md

#### About Dosu

This response is meant to be useful and save you time. It is **not meant to be a precise solution**, but rather a starting point for your own research. Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant. If you want to continue the conversation, start your reply with @dosu-bot.

[car9797]

@car9797 Do you have enough keys to complete this index job?

yes，enought

[takatost]

Hey, could you please provide the resource configuration of the container and the test cases for us to reproduce?

[dosubot[bot]]

Hi, @car9797,

I'm helping the team manage our backlog and am marking this issue as stale. From what I understand, you encountered a CPU performance spike and a 'NoneType' error while using the Jina embedding model in Dify version 0.5.8. The issue lacks expected and actual behavior details. I engaged with you, seeking more information about the error and the resource configuration of the container. takatost also requested test cases to reproduce the issue. I provided a comprehensive response, suggesting potential causes for the error and advising on system requirements and service configurations.

Could you please confirm if this issue is still relevant to the latest version of the repository? If it is, please let the team know by commenting on the issue. Otherwise, feel free to close the issue yourself, or the issue will be automatically closed in 7 days.

Thank you!