Batch deletes in Neo4jVectorGraphStore#1111
Conversation
Signed-off-by: Edwin Yu <edwinyyyu@gmail.com>
Signed-off-by: Edwin Yu <edwinyyyu@gmail.com>
|
This change makes it possible to deadlock if certain deletions are done concurrently. |
|
I deployed the version with this PR, I still see the following warning in logs
Probably we also need to increase the Neo4j connection pool size? |
The error occurred when I try deleting 6000 memories. |
This is set on the Neo4j server-side. |
In MemMachine v0.2.4, we introduced variables that let you change the connection pool size. Ensure you have the latest We use Neo4j's defaults, but you are welcome to modify and test again. @edwinyyyu, we shouldn't cause the DB to stall out like this due to a "Thundering Herd" issue from large-volume operations. This looks to be one use case we should track and resolve alongside #940, which has similar symptoms, but is caused by very high search operations rather than very large delete operations. |
Got it! Thanks for the explanation Steve! |
Purpose of the change
Deletion fails due to lack of resources or can time out.
Description
Batch deletes every 10000 rows.
Type of change
Breaks existing behavior. Now deletions are no longer atomic.
How Has This Been Tested?
Checklist
Maintainer Checklist