-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] LiteDB 5.0.10 - Maximum number of transactions reached #1976
Comments
@byteAbit0101 LiteDB has a limit of 100 open transactions at a time. If youy program happens to create a lot of these |
There are not 100 transactions open at a time, except LiteDB is not closing them. Is there any possibility to trace how many are still open or which ones weren't closed? The issue is once it's running into this exception the database file gets unusable until everything is disposed and resetup. I even managed that it's even with the dispose not working anymore and both files needed to be deleted and recreated which is critical due to potential data loss. |
Hello, I'm encountering the same error with 5.0.10 and .net 4.7 in a production database. Regards, |
Hello, Then each time I'm trying to insert in the filestorage I have this error (I'm not closing the database after the rebuild) : And then after 100 occurences of this error I get : It's like the "LiteDB ENSURE: page type must be collection page" is not closing the collection I think my problem is linked with #1958 |
Hello, Please, did anyone find a solution to this problem ? I have this issue in production. |
Hi, In LiteDB 4.x we had our own locking around the LiteDb database, and after upgrading to 5.0.16 we started seeing the application hanging trying to get the lock to the database. Caught exception: Collection 'redacted' lock timeout when entering in write mode after 00:01:00 The application would recover after this and continue working just fine, however, it seems the lock timeouts became more prevalent, and then we started seeing the max transactions reached exceptions: Caught exception: Maximum number of transactions reached After this, the application does not recover and database access is not possible at all. I suspect each time we get the lock timeout, a LiteDb transaction is hung and never released, once we get this error 100 times, we get the max transactions reached error. @lbnascimento, @mbdavid, any ideas on this problem? |
I run into this exception also on LiteDB 5.0.18
|
+1 Caught exception: Maximum number of transactions reached @mbdavid , any thoughts on this? |
On 5.0.18 and 5.0.19 I have the same. I'm going to try to revert to 5.0.17. My applications are not working anymore unfortunately |
I have the same issue on |
I had this issue on |
Note that this issue is fixed by #2435 , but the fix is not included in any release yet. We test this fix by rolling it into 5.0.19 and found that it resolves the "Maximum number of transactions reached" error, and also the DiskWriterQueue locking issue #2307 which has been preventing us from upgrading to v5. So please push for a new release (5.0.20) which includes #2435 :) |
I have the same issue. Please release the fix! |
Downgrade to v5.0.17 didn't help. |
Downgrade to 5.0.17 helped in my case. |
Had the same issue here. After deleting my log file, it no longer had the issue. My previous run was attached to a debugger which I killed the process which left a 4096kb log file. Deleting it (which was fine in my test case) resolved the issue. Bizzare... Edit: Scratch that. Ran into it again. Downgrading to v5.0.17 from v5.0.19 seems to have fixed it. |
We had the same problem after upgrading from 5.0.16 to 5.0.19. |
I use liteDB on Xamarin forms, I have the same exception in IOS but not in Android, on which platform do you use LiteDb? |
Same issue with version 5.0.19 |
Same here (5.0.19), windows 11 Pro, .NET8.0. I was performing a lot of GetCollecton<T> followed by FindAll(). Downgraded to 5.0.17 and the error did not occur. Did not try other versions. |
With 5.0.17, I get "LiteDB ENSURE: page type must be collection page" from our test suite. With 5.0.19 Maximum number of transactions reached :( We have been stuck on v4 for awhile. |
Same issue here: "LiteDB ENSURE..." with 5.0.17 and "Maximum number of transactions reached.." with 5.0.19. We are definitely stuck since v4 is also marked as vulnerable. Any expected date for new release? |
Jellyfin (10.9 released this week) has the same problem too:
|
.NET Standard 2.0
LiteDB version 5.0.10
TransactionMonitor.GetTransaction (System.Boolean create, System.Boolean queryOnly, System.Boolean& isNew)
Maximum number of transactions reached
The text was updated successfully, but these errors were encountered: