Closed sipeter closed 6 months ago
To address the issue you're facing with processing text files larger than 10M in Dify 0.6.3 using xinference, consider increasing the UPLOAD_FILE_SIZE_LIMIT
in your Docker environment configuration. This setting, by default, might not accommodate the overhead that comes with processing large files, hence the errors you're encountering.
Here's a quick guide to adjust this setting:
UPLOAD_FILE_SIZE_LIMIT
to a higher value, such as 20M
, to handle larger files.Make sure to also verify any intermediary network configurations, like reverse proxies, to support larger uploads and extended processing times. For detailed guidance, refer to the docker/docker-compose.yaml
and environments.md
documents in the Dify documentation.
To continue the conversation, mention @dosu.
Not sure about the limitation of 10M, we have a default setting to 15M. But it will raise another thing 'you will not be able to submit'. Can you provide some screenshot or the docker container logs?
An error message similar to this is given. This time, the text used is 13.9M, 5 million characters, and an error is reported after processing about 20%.
After upgrading to 0.6.4, the problem seems to be solved. I tested 2 texts larger than 10M, and no previous error message appeared. It can be processed in one go.
Self Checks
Dify version
0.6.3
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
I use xinference to access the embedding model. When processing text files exceeding 10M, an error message like: HTTPConnectionPool Max retries exceeded will appear during the process, so the error is not reported at the beginning, but during the process. When I delete the erroneous file and reload the process, the process will continue on the original basis, and an error may be reported, but as long as this action is repeated, the file will eventually be processed and the process will be displayed successfully. The same 10M text is also a model accessed through xinference. I can handle the task normally in fastgpt.
✔️ Expected Behavior
No response
❌ Actual Behavior
No response