[Bug]: valkey.exceptions.LockNotOwnedError: Cannot release a lock that's no longer owned

[dalisanxianbao]

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] Non-english title submitions will be closed directly ( 非英文标题的提交将会被直接关闭 ) (Language Policy).
• [x] Please do not modify this template :) and fill in all the required fields.

RAGFlow workspace code commit ID

none

RAGFlow image version

v0.17.2-198-g0a42e577 slim

Other environment information

infinity:v0.6.0-dev3

Actual behavior

The document parsing configuration is as follows

This error is displayed when the knowledge graph reaches 80%

The following error message is displayed when the parsing is performed again

Viewing the resolution block directly causes the infinity service to crash and automatically restart

Expected behavior

No response

Steps to reproduce

In actual behavior

Additional information

This document consumes 20 million tokens, the cost is relatively large, hope to solve as soon as possible

[dosubot[bot]]

Hello @dalisanxianbao! I'm here to help you with any bugs, questions, or contributions you have. Let's work together to resolve your issue.

The valkey.exceptions.LockNotOwnedError typically occurs when a lock is attempted to be released by a process that no longer owns it. This can happen due to various reasons, such as the lock being automatically released after a timeout, or another process having acquired the lock in the meantime. To mitigate this issue, ensure that:

1. Lock Ownership: Verify that the process attempting to release the lock is the one that acquired it. This can be done by checking the lock's ownership status before attempting to release it.

2. Timeouts: Adjust the lock timeout settings to ensure that the lock does not expire prematurely. This can help prevent the lock from being released automatically before the task is completed.

3. Error Handling: Implement robust error handling to catch and manage exceptions related to lock management. This can include retry mechanisms or logging detailed information for debugging purposes.

Regarding the connection issues with the infinity package and Thrift services, the RAGFlow system uses a retry mechanism to handle connection failures. It attempts to connect multiple times with delays in between. If the connection is not established within the specified time, it raises an exception. Ensure that:

1. Network Stability: Check the network stability and ensure that the server at the specified IP address and port is reachable and operational.

2. Service Health: Monitor the health of the Infinity service to ensure it is running and responsive. This can involve checking server logs and resource usage.

3. Configuration: Verify that the configuration settings for the Infinity service and Thrift connections are correct and optimized for your environment.

These steps should help address the lock management and connection issues you're experiencing.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}