-
-
Notifications
You must be signed in to change notification settings - Fork 97
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]: java.lang.IllegalArgumentException #551
Comments
what is interesting is that the exception that I copied above only is shown in the console. I am catching exceptions, |
I have found an out of memory exception. But I am not sure if this out of memory exception caused the exception above, or if the exception above caused the out of memory exceptions. Very hard to tell, as my logging system (timbre) does not log any exception (because this exceptions are inside konserve/datahike, and my exception handling clause does not get thiem).
|
My apologies that you ran into this problem! We have fixed a memory leak that was present with the hitchhiker-tree caching and was very likely responsible for this problem. This is fixed with recent releases if you use the persistent-sorted-set, which is strongly recommended for now also for its much better read performance. We have also fixed a bug where some exceptions in the transactor were not properly propagated, which might have been the case here. Do you have the opportunity to move over to the persistent sorted set backend and retry? |
What version of Datahike are you using?
"0.4.1480" with konserve "0.6.0-alpha3"
What version of Java are you using?
17.0.1
What operating system are you using?
Debian GNU/Linux 9.13 (stretch)
What database EDN configuration are you using?
{:store {:backend :file
:path "data/datahike-db"}
:keep-history? false}
Describe the bug
My db is running for 6 weeks live, and now I get this exception on datahike transact:
What is the expected behaviour?
no exception.
How can the behaviour be reproduced?
I could upload my datahike dump if this is of any help
The text was updated successfully, but these errors were encountered: