Skip to content
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]: Changing cache size throws exception #675

Closed
alekcz opened this issue May 10, 2024 · 1 comment · Fixed by #689
Closed

[Bug]: Changing cache size throws exception #675

alekcz opened this issue May 10, 2024 · 1 comment · Fixed by #689
Labels
bug Something isn't working triage

Comments

@alekcz
Copy link
Sponsor Contributor

alekcz commented May 10, 2024

What version of Datahike are you using?

1558

What version of Java are you using?

"21.0.3" 2024-04-16

What operating system are you using?

MacOS

What database EDN configuration are you using?

{:store {:backend :file :path dev-db :scope "datahike-database"}
                 :keep-history? true
                 :store-cache-size 10000
                 :search-cache-size 100000}

Describe the bug

When I change the cache configuration and connect to Datahike I get an exception.

Execution error (ExceptionInfo) at datahike.connector/ensure-stored-config-consistency (connector.cljc:130).
Configuration does not match stored configuration.

What is the expected behaviour?

The DB should start as normal if the search or search caches change.

How can the behaviour be reproduced?

  1. Create a DB.
  2. Transact on the DB
  3. Shutdown the DB change the cache setting
  4. Behold the error
@alekcz alekcz added bug Something isn't working triage labels May 10, 2024
@alekcz
Copy link
Sponsor Contributor Author

alekcz commented May 10, 2024

@whilo here's the issue as discussed

@alekcz alekcz changed the title [Bug]: [Bug]: Changing cache size throws exception May 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant