Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 14:13:35 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #3991] [BUG]: LanceDB commit conflict kills the docker instance #2537

New Issue
Closed
opened 2026-02-22 18:30:07 -05:00 by yindo · 3 comments
yindo commented 2026-02-22 18:30:07 -05:00
Owner
Copy Link
Copy Source

Originally created by @AndreC10002 on GitHub (Jun 12, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3991

How are you running AnythingLLM?

Docker (local)

What happened?

At time, when deleting multiple documents in multiple folders, either via UI or API, the Docker instance quits because of the following error:

node:internal/process/promises:288
triggerUncaughtException(err, true /* fromPromise */);
^

[Error: lance error: Commit conflict for version 1993: There was a concurrent commit that conflicts with this one and it cannot be automatically resolved. Please rerun the operation off the latest version of the table.
Transaction: Transaction { read_version: 1992, uuid: "63c3c1bb-3196-40be-9732-16d584ee73d6", operation: Delete { updated_fragments: [], deleted_fragment_ids: [383], predicate: "id IN ('9c8ab1ce-25d8-4c32-9a47-5d11902edc8a','2d108d54-5bdc-436e-903f-e7643ba39563')" }, blobs_op: None
, tag: None }
Conflicting Transaction: Some(Transaction { read_version: 1992, uuid: "d8026f8f-ac03-4d94-b579-b956a6c4ce76", operation: Delete { updated_fragments: [], deleted_fragment_ids: [383], predicate: "id IN ('9c8ab1ce-25d8-4c32-9a47-5d11902edc8a','2d108d54-5bdc-436e-903f-e7643ba39563')"
}, blobs_op: None, tag: None }), /home/build_user/.cargo/registry/src/index.crates.io-6f17d22bba15001f/lance-0.22.0/src/io/commit.rs:149:23
Caused by: Commit conflict for version 1993: There was a concurrent commit that conflicts with this one and it cannot be automatically resolved. Please rerun the operation off the latest version of the table.
Transaction: Transaction { read_version: 1992, uuid: "63c3c1bb-3196-40be-9732-16d584ee73d6", operation: Delete { updated_fragments: [], deleted_fragment_ids: [383], predicate: "id IN ('9c8ab1ce-25d8-4c32-9a47-5d11902edc8a','2d108d54-5bdc-436e-903f-e7643ba39563')" }, blobs_op: None, tag: None }
Conflicting Transaction: Some(Transaction { read_version: 1992, uuid: "d8026f8f-ac03-4d94-b579-b956a6c4ce76", operation: Delete { updated_fragments: [], deleted_fragment_ids: [383], predicate: "id IN '9c8ab1ce-25d8-4c32-9a47-5d11902edc8a','2d108d54-5bdc-436e-903f-e7643ba39563')" }, blobs_op: None, tag: None }), /home/build_user/.cargo/registry/src/index.crates.io-6f17d22bba15001f/lance-0.22.0/src/io/commit.rs:149:23
Caused by: There was a concurrent commit that conflicts with this one and it cannot be automatically resolved. Please rerun the operation off the latest version of the table.
Transaction: Transaction { read_version: 1992, uuid: "63c3c1bb-3196-40be-9732-16d584ee73d6", operation: Delete { updated_fragments: [],
deleted_fragment_ids: [383], predicate: "id IN ('9c8ab1ce-25d8-4c32-9a47-5d11902edc8a','2d108d54-5bdc-436e-903f-e7643ba39563')" }, blobs_op:
None, tag: None }
Conflicting Transaction: Some(Transaction { read_version: 1992, uuid: "d8026f8f-ac03-4d94-b579-b956a6c4ce76", operation: Delete { updated_fragments: [], deleted_fragment_ids: [383], predicate: "id IN ('9c8ab1ce-25d8-4c32-9a47-5d11902edc8a','2d108d54-5bdc-436e-903f-e7643ba39563')" }, blobs_op: None, tag: None })] {
code: 'GenericFailure'
}

Although I understand this is a concurrency conflict on LanceDB, the exception should be treated appropriately without disrupting the entire system.

Are there known steps to reproduce?

Upload documents to multiple folders and try to delete them all together via the UI, or issue API DELETE commands for the files.

Originally created by @AndreC10002 on GitHub (Jun 12, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3991 ### How are you running AnythingLLM? Docker (local) ### What happened? At time, when deleting multiple documents in multiple folders, either via UI or API, the Docker instance quits because of the following error: node:internal/process/promises:288 triggerUncaughtException(err, true /* fromPromise */); ^ [Error: lance error: Commit conflict for version 1993: There was a concurrent commit that conflicts with this one and it cannot be automatically resolved. Please rerun the operation off the latest version of the table. Transaction: Transaction { read_version: 1992, uuid: "63c3c1bb-3196-40be-9732-16d584ee73d6", operation: Delete { updated_fragments: [], deleted_fragment_ids: [383], predicate: "id IN ('9c8ab1ce-25d8-4c32-9a47-5d11902edc8a','2d108d54-5bdc-436e-903f-e7643ba39563')" }, blobs_op: None , tag: None } Conflicting Transaction: Some(Transaction { read_version: 1992, uuid: "d8026f8f-ac03-4d94-b579-b956a6c4ce76", operation: Delete { updated_fragments: [], deleted_fragment_ids: [383], predicate: "id IN ('9c8ab1ce-25d8-4c32-9a47-5d11902edc8a','2d108d54-5bdc-436e-903f-e7643ba39563')" }, blobs_op: None, tag: None }), /home/build_user/.cargo/registry/src/index.crates.io-6f17d22bba15001f/lance-0.22.0/src/io/commit.rs:149:23 Caused by: Commit conflict for version 1993: There was a concurrent commit that conflicts with this one and it cannot be automatically resolved. Please rerun the operation off the latest version of the table. Transaction: Transaction { read_version: 1992, uuid: "63c3c1bb-3196-40be-9732-16d584ee73d6", operation: Delete { updated_fragments: [], deleted_fragment_ids: [383], predicate: "id IN ('9c8ab1ce-25d8-4c32-9a47-5d11902edc8a','2d108d54-5bdc-436e-903f-e7643ba39563')" }, blobs_op: None, tag: None } Conflicting Transaction: Some(Transaction { read_version: 1992, uuid: "d8026f8f-ac03-4d94-b579-b956a6c4ce76", operation: Delete { updated_fragments: [], deleted_fragment_ids: [383], predicate: "id IN '9c8ab1ce-25d8-4c32-9a47-5d11902edc8a','2d108d54-5bdc-436e-903f-e7643ba39563')" }, blobs_op: None, tag: None }), /home/build_user/.cargo/registry/src/index.crates.io-6f17d22bba15001f/lance-0.22.0/src/io/commit.rs:149:23 Caused by: There was a concurrent commit that conflicts with this one and it cannot be automatically resolved. Please rerun the operation off the latest version of the table. Transaction: Transaction { read_version: 1992, uuid: "63c3c1bb-3196-40be-9732-16d584ee73d6", operation: Delete { updated_fragments: [], deleted_fragment_ids: [383], predicate: "id IN ('9c8ab1ce-25d8-4c32-9a47-5d11902edc8a','2d108d54-5bdc-436e-903f-e7643ba39563')" }, blobs_op: None, tag: None } Conflicting Transaction: Some(Transaction { read_version: 1992, uuid: "d8026f8f-ac03-4d94-b579-b956a6c4ce76", operation: Delete { updated_fragments: [], deleted_fragment_ids: [383], predicate: "id IN ('9c8ab1ce-25d8-4c32-9a47-5d11902edc8a','2d108d54-5bdc-436e-903f-e7643ba39563')" }, blobs_op: None, tag: None })] { code: 'GenericFailure' } Although I understand this is a concurrency conflict on LanceDB, the exception should be treated appropriately without disrupting the entire system. ### Are there known steps to reproduce? Upload documents to multiple folders and try to delete them all together via the UI, or issue API DELETE commands for the files.
yindo added the possible bugneeds info / can't replicate labels 2026-02-22 18:30:07 -05:00
yindo closed this issue 2026-02-22 18:30:07 -05:00
yindo commented 2026-02-22 18:30:07 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jun 12, 2025):

What kind of system are you using, because I can mass delete files in one go across many folders and more and have no issue. Doing this on mac, docker, and Ubuntu/Docker

@timothycarambat commented on GitHub (Jun 12, 2025): What kind of system are you using, because I can mass delete files in one go across many folders and more and have no issue. Doing this on mac, docker, and Ubuntu/Docker
yindo commented 2026-02-22 18:30:07 -05:00
Author
Owner
Copy Link
Copy Source

@AndreC10002 commented on GitHub (Jun 12, 2025):

I am running AnythingLLM on Docker on Debian 12.8. Server has 8 CPUs, 192GB of RAM and SSDs.

Is there any additional information i can provide to assist debugging this?

@AndreC10002 commented on GitHub (Jun 12, 2025): I am running AnythingLLM on Docker on Debian 12.8. Server has 8 CPUs, 192GB of RAM and SSDs. Is there any additional information i can provide to assist debugging this?
yindo commented 2026-02-22 18:30:08 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jun 13, 2025):

Then that is obviously plenty of compute to do things quickly. Is there an estimate of how many files you are managing to delete at once that might help drive replication?

@timothycarambat commented on GitHub (Jun 13, 2025): Then that is obviously plenty of compute to do things quickly. Is there an estimate of how many files you are managing to delete at once that might help drive replication?
yindo changed title from [BUG]: LanceDB commit conflict kills the docker instance to [GH-ISSUE #3991] [BUG]: LanceDB commit conflict kills the docker instance 2026-06-05 14:47:08 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label needs info / can't replicate possible bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#2537
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?